Skip to content
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

[FEATURE] Managing IAS via Terraform #749

Open
lechnerc77 opened this issue Mar 21, 2024 · 10 comments
Open

[FEATURE] Managing IAS via Terraform #749

lechnerc77 opened this issue Mar 21, 2024 · 10 comments
Labels
enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion.

Comments

@lechnerc77
Copy link
Member

What area do you want to see improved?

other

Is your feature request related to a problem? Please describe.

Currently the Terraform Provider supports all resources and configurations exposed via the BTP CLI.
In order to enable an end2end flow especially from the perspective auf security setup and IAS perspective it would be great to have a dedicated provider for the SAP IAS i.e. its configuration.

Describe the solution you would like

A dedicated provider for IAS configuration exists and can be combined with the existing providers like the one for SAP BTP to enable end2end provisioning flows.

Describe alternatives you have considered

Usage of APIs for IAS, which is a workaround but breaks the IaC/Terraform flow

Additional context

n/a

@lechnerc77 lechnerc77 added enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion. labels Mar 21, 2024
Copy link

Thanks for the feature request. We evaluate it and update the issue accordingly.

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@CHERIANS
Copy link
Contributor

SAP Cloud Identity Service API's https://api.sap.com/package/SCPIdentityServices/rest

@lechnerc77
Copy link
Member Author

lechnerc77 commented Apr 23, 2024

Example for a scenario that we heard from customers is the combination of Microsoft Entra ID and IAS to secure their system landscape. The setup procedure they follow is described in the Microsoft documentation: https://learn.microsoft.com/en-us/entra/fundamentals/scenario-azure-first-sap-identity-integration. This configuration should be rolled out in a stable and repeatable manner.

According to the customer feedback the configuration is done leveraging a two stage approach for IAS. The setup reflects the organizational structure of the customers. Consequently, the configuration might differ per legal entity and/or org unit.

@lechnerc77
Copy link
Member Author

To the supporters of this request @olfolfolf, @Kaefermade, @jumu75, @BerndReichel, @sebastianesch, @ChristianAicher, @SeanKilleen, and @rothandreas: Would be great if you could add the scenarios you would like to see the provider in your setup and challenges you are currently facing because you are not having this provider.

@jumu75
Copy link

jumu75 commented Apr 23, 2024

Hi @lechnerc77,

we are a company with a lot of Auxiliary workers which have no Active Directory account and they should leverage the IAS for external Authentication to use SAP BTP applications.
The manager and supervisors of newly employed Auxiliary workers should use a tool like e.g. Microsoft Forms to input all necessary account information like surname, last name, login, privat E-Mail address.
With this information we want to use Terraform to automatically create IAS User for authentication.

It would be great if such a solution could be possible.

Thanks in
Best regards
Jürgen

@rothandreas
Copy link

Hi @lechnerc77,
Focus for me would be the IAS Tasks to be done to finalize the Setup of a new Subaccount. Means Config of IAS Applications - nothing else.
Benefit: One Tool (Terraform) who could handle End to End Setup of an Subaccount (Avoiding using Cli´s were possible)

A Provider who would be capable of setting the following Values:

  1. IAS Application Name/Settings
  2. Set Values in Subject Name Identifier
  3. Apply Function to Subject Name Identifier
  4. Conditional Authentication -> "Default Authenticating Identity Provider"

Would be good enough for us
Andreas

@SeanKilleen
Copy link
Contributor

@lechnerc77 I'll do my best to give a quick summary, happy to go deeper.

We provide two subaccounts to our customers for the 05-Deliver and 06-Consume scenarios in which they consume our application from the marketplace. We allow customers to bring whatever IdP is supported by CIS. Automating as much of that setup as possible would be great. My goal is to be able to add the requisite information to a terraform config for an incoming client and have the 05 and 06 environment be provisioned according to their needs.

@lechnerc77
Copy link
Member Author

@SeanKilleen @rothandreas @jumu75 Thanks a lot for your fast responses and the sceanrios!

@sebastianesch
Copy link

Hi @lechnerc77,

I would like to extend the scenario from Andreas and also additionally configure the Attributes sent to the Application and create Authorization Policies for Applications / create Groups in Cloud Identity Service.

This would allow to automate the complete Subaccount / Application onboarding process.

Kind regards,
Sebastian

@ChristianAicher
Copy link

ChristianAicher commented Apr 25, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion.
Projects
None yet
Development

No branches or pull requests

7 participants