11 docs tagged with "oauth2"

This guide provides step-by-step instructions on integrating Auth0 as an identity provider for your application.

This flow is good for applications that cannot securely store a client_secret, such as single-page applications (SPAs), mobile apps, and desktop applications.

This guide provides step-by-step instructions on integrating Microsoft Azure Active Directory (Azure AD) as an identity provider for your Project.

The Client Credentials grant is designed for machine-to-machine (M2M) authentication where no user interaction is required. This flow is used when applications need to access their own resources or when acting on behalf of themselves rather than a user.

Client registration is the process of creating OAuth 2.0/OpenID Connect client applications in Haste Health. Clients represent applications that need to authenticate users or access resources on the FHIR server.

This guide provides step-by-step instructions on integrating Google Cloud Platform (GCP) as an identity provider for your Project.

This guide provides step-by-step instructions on integrating a seperate Haste Health tenant as an identity provider for your Project.

This guide provides step-by-step instructions on integrating Keycloak as an identity provider for your Project.

This guide provides step-by-step instructions on integrating Okta as an identity provider for your Project.

The Refresh Token grant allows applications to obtain new access tokens without requiring the user to re-authenticate. This is essential for maintaining long-lived sessions while keeping access tokens short-lived for security.

Haste Health implements a comprehensive scope system that combines OpenID Connect (OIDC) scopes with SMART on FHIR scopes to provide fine-grained access control for healthcare applications.