-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback for "Setting Up Authentication" #19
Comments
Thanks a lot for the feedback. Our colleague @ValAta will look into this. |
Hi Anna, any updates on this topic? Thanks a lot, |
Hi @ncktz-cbs, |
Hi Nico, |
Hi Valentin, during the DSAG technology days, we had various discussions with SAP colleagues. They also see the sense of more granular recommendation of the future IAS setup: this includes not only the landscape but also topics such as when user provisioning is required. Thanks a lot |
Hi Nico, |
Hi Valentin, Can you plesae reopen this ticket until the described discussion is completed and IAS-specific best practices have been added to the best practice guide? Thanks a lot |
Hi Nico, |
Hi Nico, |
Hi Valentin, feel free to reach out to your colleague Regine Schimmer. So far, we are still waiting for any suggestions from SAP. Best regards |
@ValAta : This issue has been open for 96 days - do you have any update? Thanks! |
Hi @je-hal, |
Hi Nico,
|
Hi @ncktz-cbs, |
Thanks, Valentin! As communicated directly to your colleagues, I think it's a great first step into the right direction. Looking forward to additional updates to the best practice guide that adress the remaining open points. |
Hi @ncktz-cbs |
https://help.sap.com/docs/btp/best-practices/setting-up-authentication
According to slide 20 of the SAP S/4HANA Cloud 3-system landscape - Onboarding Guide, SAP recommends to connect the non-productive IAS to the non-productive S/4HANA Cloud environments and the productive IAS to the productive S/4HANA Cloud environment and CALM.
Unfortunately, we cannot find any clear recommendation for the IAS setup for BTP. Do you recommend the same setup here (non-productive IAS for non-productive subaccounts, productive IAS for productive accounts)? Even for dev or test environments, we work with ‘productive’ identities. For this reason and from our point of view, these subaccounts should be connected to a productive IAS or at least the productive Azure AD. According to our experience, the non-productive AD is usually just used for internal testing purposes and never connected to any enterprise applications.
If this is SAP’s recommendation, this also means that the configuration effort for groups and groups assignments doubles compared to the setup of just using the productive IAS for all subaccounts that we usually see. Or is there any transport mechanism for delta changes planned from one IAS to another that could reduce these efforts? Alternatively, the groups could be assigned in AD, but as of our understanding SAP’s strategic recommendation is to assign the groups in the IAS and not in AD, is this correct?
The text was updated successfully, but these errors were encountered: