Hello Creatio Community,
I am currently working on a Python application that extracts data from the Creatio API using the OData protocol. The application has been successfully tested in our quality environment, where it functions flawlessly. However, as I prepare to deploy the application in our production environment, I need some clarification on how to handle SSO (Single Sign-On) authentication for API access.
Here are the key details and questions:
User Account for Authentication:
In our production environment, which uses SSO, should I use a Creatio user account that is specifically added to the SSO group, or can I continue using a regular Creatio production user account, as I did successfully in the quality environment without SSO?
API Authentication Configuration:
For SSO-based authentication in the production environment, is there any additional configuration required in the API call setup compared to what is recommended in the Creatio documentation for environments without SSO?
Here is the reference to the documentation I’m following: https://documenter.getpostman.com/view/10204500/SztHX5Qb#46f97170-d66d-4ed9-8941-08590bcdf444.
Environment Links for Reference:
If there are any best practices or specific considerations when transitioning from a non-SSO environment to an SSO-enabled production environment, I would greatly appreciate any insights. This includes potential pitfalls, user account configurations, and any modifications required in the API requests when dealing with SSO.
Thank you in advance for your support and guidance!