providers/eveonline
EVEOnlineProfile
Extends
Record<string,any>
Properties
CharacterID
CharacterID: number;CharacterName
CharacterName: string;CharacterOwnerHash
CharacterOwnerHash: string;ExpiresOn
ExpiresOn: string;IntellectualProperty
IntellectualProperty: string;Scopes
Scopes: string;TokenType
TokenType: string;default()
default<P>(options): OAuthConfig<P>Add EveOnline login to your page.
Setup
Callback URL
https://example.com/api/auth/callback/eveonlineConfiguration
import { Auth } from "@auth/core"
import EveOnline from "@auth/core/providers/eveonline"
const request = new Request(origin)
const response = await Auth(request, {
providers: [
EveOnline({
clientId: EVEONLINE_CLIENT_ID,
clientSecret: EVEONLINE_CLIENT_SECRET,
}),
],
})Resources
Notes
When creating your application, make sure to select Authentication Only as the connection type.
If using JWT for the session, you can add the CharacterID to the JWT and session. Example:
options: {
jwt: {
secret: process.env.JWT_SECRET,
},
callbacks: {
session: async ({ session, token }) => {
session.user.id = token.id;
return session;
}
}
}By default, Auth.js assumes that the EveOnline provider is based on the OAuth 2 specification.
The EveOnline 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 EVEOnlineProfile |
Parameters
| Parameter | Type |
|---|---|
options | OAuthUserConfig<P> |
Returns
OAuthConfig<P>