Use existing UAA instead of deploy to fix #2 #3
Conversation
|
I don't understand the reason for this change. If the project is packaged as an MTA then you would want it to also create the UAA instance. This change would remove that feature. |
|
Hi Thomas,
I noticed this behaviour that MTA creates the UAA but doesn’t add the
scopes/ role templates to app runtime.
So it is required to create the UAA manually in advance for scopes/ role to
be created. I guess, it is restricted from developer’s hand and
CD-security.json only added to WebIDE project for best practices / version
control.
Also, there is bug in SPS 03 that doesn’t allow app build for web module if
UAA is created in advance that might be the reason Gregor added it as
existing service. This issue is fixed in SPS04.
Thanks,
Tarun
…On Wed, Feb 26, 2020 at 7:58 AM Thomas Jung ***@***.***> wrote:
I don't understand the reason for this change. If the project is packaged
as an MTA then you would want it to also create the UAA instance. This
change would remove that feature.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3?email_source=notifications&email_token=AC2L5AGKQ3GQE3QPYPOVLZTREZ7PXA5CNFSM4K4ASAOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENARQ6I#issuecomment-591468665>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2L5AAOEMWRI77E3WU27PLREZ7PXANCNFSM4K4ASAOA>
.
|
That should not be the case. In 2.0 SPS 04 at least it does work. If the xs-security.json is in the project and referenced in the mta.yaml then the UAA is created correctly and the scopes/attributes/role templates are all correctly generated. |
|
It doesn't work for me I tried in HANA onPrem 2.0 SPS 04 (version 45). MTAR
deploy creates UAA , binds web and srv modules to UAA but scopes,
attributes and role templates doesn't get generated.
I have to always create UAA manually for generation of generation of
scopes/attributes/role templates.
Is there any environment variable that needs to be set to enable / disable
generation of scopes/attributes/role templates from app build ?
…On Wed, 26 Feb 2020 at 08:43, Thomas Jung ***@***.***> wrote:
I noticed this behaviour that MTA creates the UAA but doesn’t add the
scopes/ role templates to app runtime.
That should not be the case. In 2.0 SPS 04 at least it does work. If the
xs-security.json is in the project and referenced in the mta.yaml then the
UAA is created correctly and the scopes/attributes/role templates are all
correctly generated.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3?email_source=notifications&email_token=AC2L5AGTXHIAEPZQGN3ACADRE2E3RA5CNFSM4K4ASAOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENAXOKI#issuecomment-591492905>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC2L5AHJDBRA5A3AZDP7KJTRE2E3RANCNFSM4K4ASAOA>
.
|
|
I just did a project and it worked. Just make sure the parameter properly references the xs-security.json. Oh and you probably want to use the standalone Cloud mta build tool. I know at one point the builder in the Web IDE didn't package the xs-security.json into the mtar correctly. I was pretty sure that was fixed now. However I know for sure the standalone cloud mta build tool does package it correctly. I have a recent project that does rely upon it. |
No description provided.