Re: [Architecture] [IAM] Export and Import Service Provider as file

Hi all, We have finalized to use event handlers to validate the service provider and pass the configurations between application module with other inbound authentication modules. Please find the flow of the import application, [image: image.png] Here we are calling the doPreUpdateApplication li

Re: [Architecture] [IAM] Export and Import Service Provider as file

Hi Malithi, yes, we can implement as you suggest. My concerns are - We are validating the claims, authenticators, identity providers and inbound authenticator configuration during import. This will also cause new cyclic dependency, then we need to fix this using the same handler appro

Re: [Architecture] [IAM] Export and Import Service Provider as file

Hi Senthalan, One other option would be to move export functionality of the respective inbound authenticator configuration for the inbound component and to get them plugged to the application management component as handlers. So that, the export connector contract will be defined in the applicatio

Re: [Architecture] [IAM] Export and Import Service Provider as file

Hi all, We have decided to export the "Inbound Authentication Configuration" and omit any secret values with the user confirmation in UI when exporting. To inject the inbound authentication configuration, we need the OAuth and SAML configurations of the application. But getting these configuration

[Architecture] [IAM] Export and Import Service Provider as file

Hi all, I am working on the importing and exporting service provider as an xml file. Currently, we support file-based DAO for service providers. But, this new implementation allows users to export service provider and then import back through the UI. Then it will be synced with the database. This