providers/ztrust
ztrustProfile
Extends
Record<string,any>
Indexable
[key: string]: any
Properties
acr
acr: string;at_hash
at_hash: string;aud
aud: string;auth_time
auth_time: number;azp
azp: string;email: string;email_verified
email_verified: boolean;exp
exp: number;family_name
family_name: string;given_name
given_name: string;groups?
optional groups: string[];iat
iat: number;iss
iss: string;jti
jti: string;name
name: string;picture
picture: string;preferred_username
preferred_username: string;session_state
session_state: string;sid
sid: string;sub
sub: string;typ
typ: string;user
user: User;default()
function default<P>(options): OIDCConfig<P>Add Ztrust login to your page.
Setup
Callback URL
https://example.com/api/auth/callback/ztrustConfiguration
import { Auth } from "@auth/core"
import Ztrust from "@auth/core/providers/ztrust"
const request = new Request(origin)
const response = await Auth(request, {
providers: [
Ztrust({
clientId: ZTRUST_CLIENT_ID,
clientSecret: ZTRUST_CLIENT_SECRET,
issuer: ZTRUST_ISSUER,
}),
],
})Resources
Create an openid-connect client in Ztrust with “confidential” as the “Access Type”.
issuer should include the realm – e.g. https://ztrust-domain.com/realms/My_Realm_name
Notes
By default, Auth.js assumes that the Ztrust provider is based on the Open ID Connect specification.
The Ztrust provider comes with a default configuration. To override the defaults for your use case, check out customizing a built-in OAuth provider.
Disclaimer If you think you found a bug in the default configuration, you can open an issue.
Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec, we might not pursue a resolution. You can ask for more help in Discussions.
Type Parameters
| Type Parameter |
|---|
P extends ztrustProfile |
Parameters
| Parameter | Type |
|---|---|
options | OIDCUserConfig<P> |
Returns
OIDCConfig<P>