Welcome to OneAuxilia Docx

Find all the guides and resources you need to develop with OneAuxilia.

OneAuxilia builds beautifully simple dev-acceleration infrastructure for SaaS teams. We provide an easy-to-use platform and code support for building:

• Authentication and Access

• Environment management

• Social Connection

• User management

• B2B/B2B2C infrastructure

• Webhooks and connections

• Custom data, tokens, pages, and domains

• Machine to Machine (M2M) Authorization (coming soon)

OneAuxilia for different strategy auth concept

Authentication Method

Some popular authentication strategy for your applications:

Session Based Authentication: In Session Based Authentication, the server will create a session for the user after the user logs in. Session ID will be saved in a cookie in the user's browser. While the user is still logged in, the cookie will continue to be sent with subsequent requests. The server can compare the session ID stored in the cookie with the session stored in memory to verify user information and send a response with the corresponding status.

Token Authentication: Some websites use JSON Web Token (JWT) instead of session authentication. In Token Based Authentication, the server secretly generates a JWT and sends the JWT to the client. The client saves the JWT (usually local storage) and adds the JWT to the header with every request. The server will then authenticate the JWT with every request from the client and return a response. When to use: Ideal for more secure and scalable systems, especially when avoiding sending login credentials with each request is a priority.

OAuth Authentication: Enables third-party limited access to user resources without revealing credentials by issuing access tokens after user authentication. When to use: Ideal for scenarios requiring controlled access to user resources by third-party applications or services.

API Key Authentication: Assigns unique keys to users or applications, sent in headers or parameters; while simple, it might lack the security features of token-based or OAuth methods. When to use: Convenient for straightforward access control in less sensitive environments or for granting access to certain functionalities without the need for user-specific permissions.

By offering IDM as a third-party service, we will use sessions as JWT keys to provide our clients with a convenient and efficient way to manage user information. This approach also enables advanced features such as device access control without altering the session-based or token-based concepts. This way, users can either use the default JWT method or customize JWT templates to encrypt user information, which is then packaged within the session.

To enhance your application's security and user experience, OneAuxilia allows extensive customization. Utilize the Dashboard under the User & Authentication section to configure settings such as login methods, editable user properties, access control, and customize notification messages sent during authentication processes.

Configuration: OneAuxilia's configuration settings affect how the users of your application can sign up and sign in and which properties are editable via their user profile. You can also manage user sessions, control who gets access to your application, and customize the email & SMS messages that are sent by Clerk during authentication flows. All of these settings can be found under the User & Authentication section in the OneAuxilia's Dashboard