Identity Service

the nativewaves cloud documentation is currently under construction please contact us if you have questions and need further assistance the identity service offered by nativewaves is an implementation of an openid connect provider that focuses on providing authentication services its primary purpose is to seamlessly integrate user identity management into our application and services, ensuring secure access for users you can either create a nativewaves user account or utilize existing accounts from external identity providers like microsoft azure ad/office 365 for more in depth information regarding the rest api of this service, we encourage you to check the swagger api documentation this comprehensive page outlines the various endpoints, parameters, and responses of the api key features user authentication the identity service facilitates user authentication by giving out identity, access and refresh tokens after successful login these tokens are json web tokens (jwts) that are summarized in the following overview identity tokens identity tokens, contain information about the authenticated user's identity they typically include details such as user id, name, and other relevant attributes identity tokens are primarily used to verify the identity of the user during authentication processes and are usually short lived in the context of a nativewaves api, identity tokens are not directly used for interacting with the api instead, they are primarily used by the user application to retrieve information about the authenticated user access tokens access tokens are issued to authenticated users after a successful login access tokens are usually included in the authorization header of nativewaves api requests and are validated by the server to ensure that the user has the necessary permissions they have a limited lifespan to enhance security and are associated with a specific set of scopes that define the level of access granted refresh tokens refresh tokens are long lived tokens that are provided alongside an access token during authentication while access tokens have a limited lifespan, refresh tokens are designed to be used to obtain new access tokens once the original token expires they serve as a secure mechanism to request fresh access tokens without requiring the user to reauthenticate refresh tokens are typically kept in a secure storage, such as an http only cookie, and are used to request new access tokens when needed user information retrieval with the identity service, you or a nativewaves application can retrieve detailed user information this information may include the user's name, email address, and other relevant attributes like profile picture, depending on the scope and permissions granted user authentication options authentication via jwt tokens when authenticating a user within a nativewaves application like the nativewaves console, the normal login flow is followed this involves the user logging in using their nativewaves user account credentials (email and password) or an external identity provider after successful authentication, the application utilizes the different jwt tokens (identity, access, and refresh tokens) retireved after login to ensure that the user remains logged in and authenticated authentication via api keys (upcoming) this feature is not implemented yet and will be part of a future release api keys offer a simpler alternative to managing jwt tokens, allowing programmatic access to nativewaves services in the nativewaves console, users will be able to create and manage api keys, which can be used in api requests instead of jwt tokens authentication via custom openid connect provider (upcoming) this feature is not implemented yet and will be part of a future release in addition to api keys, nativewaves offers the capability to integrate a custom openid connect provider with an existing nativewaves user account this feature allows you to authenticate a nativewaves user by using a jwt bearer token from your own openid connect provider to enable this authentication method, you can specify certain attributes (such as issuer, audience, subject id, etc ) in the nativewaves console that require a match between the jwt bearer token and the nativewaves user account by configuring these attributes, you can establish a trusted connection between your custom openid connect provider and nativewaves, allowing seamless authentication for nativewaves users this method eliminates the need to store api keys and allows you to reuse your existing openid connect security system when interacting with nativewaves services and apis