Dear all,
I’m currently implementing OIDC authentication in a personal environment using this Forge. However, it takes about 20 seconds from the start of authentication to completion.
If anyone has applied this Forge in a production environment, I would greatly appreciate it if you could share the following information:
Your insights will help us establish a reference for implementing this solution. Thank you in advance for your assistance!
Which OIDC provider have you integrated? Where exactly is the time being spent when redirecting to the login page of the provider from your OutSystems application?
The redirection to the OIDC provider typically happens through the Global Exception Handler, after which control is entirely transferred to the OIDC provider (e.g., Google, LinkedIn, etc.).
To identify where the time is being spent, you can profile the redirection using the Network tab in your browser's developer tools.
Hi @Ayako Shiratori,
The performance on the personal environment for the first request does not reflect the experience you will see in a production environment.Besides that, there is some caching logic involved that will only be noticeable in subsequent requests.For example, if you are using a client secret, the key that it is used to decrypt the client secret will only be added to the cache on a second request.In any case you can confirm that on your personal environment by going to the ScreenRequests and search for the one that calls the OIDC Client "Get_Authorization_URL".Regards,