oauth2authserver

Version

OAuth2/OIDC authorization server endpoints (auth/token/userinfo/revocation/.well-known) with session + consent/login UI.
oauth2authserver:
issuer: https://auth.example.com
location: logindialog
consentFile: conf/consent.html
userDataProvider: {}
clientList: {}
claimList: {}
oauth2authserver:
    issuer: https://auth.example.com
    location: logindialog
    consentFile: conf/consent.html
    userDataProvider: {}
    clientList: {}
    claimList: {}

Syntax

oauth2authserver:
issuer: <string> # required
'$ref': <string>
accountBlocker: {}
bearerJwtToken: {}
bearerToken: {}
cachingUserDataProvider: {}
claims: {}
consentFile: <string>
customStatementJdbcUserDataProvider: {}
exposeUserCredentialsToSession: <boolean>
htpasswdFileProvider: {}
issueNonSpecIdTokens: <boolean>
issueNonSpecRefreshTokens: <boolean>
jdbcUserDataProvider: {}
ldapUserDataProvider: {}
location: <string>
message: <string>
path: <string>
refresh: {}
sessionManager: {}
staticClientList: {}
staticUserDataProvider: {}
unifyingUserDataProvider:
- <userDataProviders>
oauth2authserver:
  issuer: <string> # required
  '$ref': <string>
  accountBlocker: {}
  bearerJwtToken: {}
  bearerToken: {}
  cachingUserDataProvider: {}
  claims: {}
  consentFile: <string>
  customStatementJdbcUserDataProvider: {}
  exposeUserCredentialsToSession: <boolean>
  htpasswdFileProvider: {}
  issueNonSpecIdTokens: <boolean>
  issueNonSpecRefreshTokens: <boolean>
  jdbcUserDataProvider: {}
  ldapUserDataProvider: {}
  location: <string>
  message: <string>
  path: <string>
  refresh: {}
  sessionManager: {}
  staticClientList: {}
  staticUserDataProvider: {}
  unifyingUserDataProvider:
    - <userDataProviders>

Attributes

NameRequiredDefaultDescriptionExamples
$reffalse-Reference a component defined under components.-
consentFilefalse---
exposeUserCredentialsToSessionfalse---
issueNonSpecIdTokensfalsefalseIssue id-tokens also in credentials-flow and password-flow . The OIDC specification, which brings in id-tokens, does not handle those flows, which is why the default value is false.-
issueNonSpecRefreshTokensfalsefalseIssue refresh-tokens also in credentials-flow. The OAuth2 specification does not issue refresh tokens in the credentials-flow, which is why the default value is false.-
issuertrue---
locationfalse-Base path under which the login dialog will be served.logindialog
messagefalse---
pathfalse---

Child Structure

ElementCardinalityDescription
accountBlocker0..1Keeps track of blocked user accounts (accounts become blocked after too many failed logins).
bearerJwtToken0..1
bearerToken0..1
cachingUserDataProvider0..1Caching User Data provider caches previous successful logins in order to make authentication faster
claims0..1
customStatementJdbcUserDataProvider0..1
htpasswdFileProvider0..1A user data provider utilizing htpasswd-style files.
jdbcUserDataProvider0..1
ldapUserDataProvider0..1A user data provider querying an LDAP server to authorize users and retrieve attributes.
refresh0..1
sessionManager0..1Explanation:
staticClientList0..1
staticUserDataProvider0..1A user data provider listing all user data in-place in the config file.
userDataProviders0..*

Can be used in