<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009xnEt5CAEOkta Classic EngineIntegrationsAnswered2025-09-13T09:01:51.000Z2024-01-19T05:39:34.000Z2024-01-22T09:11:56.000Z
Addressing Performance Issues: Okta SAML 2 Integration Impact on Spring Boot App API and Web Server Response Times

Have the integration of a Spring Boot app with Okta SAML 2 resulted in increased API response time and web server response time, compared to the normal and good response times observed before integration? What steps should be taken to address this issue—should adjustments be made in the Okta Developer Console or in the backend code? I am currently using the Okta Developer trial version.


  • a0n5s (a0n5s)

    increased API response time and web server response time, what this means? your application's response time? what it done before response with okta?

This question is closed.
Loading
Addressing Performance Issues: Okta SAML 2 Integration Impact on Spring Boot App API and Web Server Response Times