> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/identity-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/identity-support/integration/integration-document/idp-integration/faq.md). # FAQ #### 1. What is an Integration Application? An Integration Application is a secure connection between your system and Oten Identity.\ It allows your users to log in using Oten and enables Oten to manage authentication for your app. *** #### 2. Why do I need to create an integration application? You need an integration application to: * Enable **Login with Oten** * Securely authenticate users * Control access to your system It is required for any system that wants to use Oten Identity. *** #### 3. Who should create an integration application? This guide is suitable for: * Organization admins * IT admins You do **not** need to be a developer to get started. *** #### 4. Do I need technical knowledge to create an integration application? No.\ Oten provides a guided onboarding flow with clear instructions.\ Technical setup is explained step by step, and no coding is required at the beginning. *** #### 5. Where should I start if I am new? Start from [**https://oten.com**](https://oten.com): * Go to **Products → Single Sign-On**, or * Click **Start Integration** on the landing page From there, Oten will guide you through the process. *** #### 6. Do I need to create an application before onboarding? No.\ The integration application is created **during the onboarding flow**.\ You don’t need to prepare anything in advance. *** #### 7. What happens during the onboarding process? During onboarding, you will: * Register your application at Oten developer portal, * Receive a client ID and client secret, * Configure redirect and logout URLs, * View integration guidance, * Test the login flow. *** #### 8. What is a client ID and client secret? They are secure credentials generated by Oten: * **Client ID** identifies your application * **Client secret** is used to authenticate your app securely These credentials are required for login integration. *** #### 9. What is a client and why do I need one? A client represents how your application connects to Oten Identity.\ Each client is configured based on how your app is built (web, mobile, frontend-only, etc.). *** #### 10. How do I choose the correct client type? Choose based on your application architecture: * **Single Page Application (SPA)**: Browser-based apps without a backend * **Regular Web Application**: Apps with a backend server handling login * **Native Application**: Mobile or desktop apps Oten provides guidance to help you choose the right option. *** #### 11. Can I change or add clients later? Yes.\ You can create and manage multiple clients for the same application at any time. *** #### 12. What is this application used for today? Today, the integration application is used to: * Enable Login with Oten * Secure authentication * Control access to your system *** #### 13. What can this application be used for in the future? The same application can later be extended to: * Manage user roles and permissions * Enable social login and enterprise SSO * Publish your app to the Oten Marketplace * Integrate with other Oten ecosystem apps *** #### 14. Is my application public after creation? No.\ By default, integration application are private and only used by your organization. Publishing to the ten Store is optional and can be done later. *** #### 15. Do I need a Workspace to create an integration application? Yes.\ You must have access to a Workspace to create and manage applications in the Oten Developer Portal. *** #### 16. Can non-developers complete the onboarding? Yes. It is coming soon.\ The onboarding flow is designed for non-technical users, with clear explanations and minimal required input. *** #### 17. What if I am not ready to integrate right now? You can stop at any step and return later.\ Your progress and created applications are saved in the Developer Portal. *** #### 18. Is this integration secure? Yes.\ Oten uses industry-standard **OAuth 2.0 and OpenID Connect** to ensure secure authentication and data protection. *** #### 19. Can I test the login flow before going live? Yes.\ Oten provides testing guidance so you can validate the end-to-end login flow before releasing it to users. *** #### 20. Where can I find help if I get stuck? You can: * Check the documentation at each Learn more hyperlink * Follow in-app guidance during onboarding * Contact Oten support if additional help is needed at .