Service Management

A service represents one authorization server instance. All settings that define your authorization server’s behavior — supported grant types, token expiration, signing keys, endpoint configuration, and so on — belong to a service. Clients and tokens always live inside a service.

​

Service Management APIs

Service retrieval, listing, and updates are served on the Authlete API host: Day-to-day configuration is usually done in the Authlete Management Console; the APIs are useful for automation such as infrastructure-as-code pipelines and environment replication.

​

Creating and deleting services (IdP Endpoint)

Service creation and deletion live on a separate host — the IdP Endpoint — and require an Organization Token. On Shared Cloud the IdP host is login.authlete.com. On Dedicated Cloud and Self-Managed (on-premises) deployments, replace login.authlete.com with the IdP host of your environment. Calling service creation directly against the Authlete API host creates the service but does not link it to your organization — the service will not appear in the Console and cannot be operated with Organization Tokens. Always use the IdP Endpoint for creation and deletion.

​

What a Service Defines

Service settings cover, among others:

• Supported grant types, response types, and scopes
• Token settings — formats and expiration of access tokens, refresh tokens, and ID tokens
• Endpoint URLs published in the discovery document
• Keys for signing and encryption (JWK Set)

For a walk-through of the individual settings, see Service Management Guide.

​

Next Steps

• Client Management — registering clients in your service
• Token Management — operating on tokens issued by your service