docs/content/integration/openid-connect/clients/meshcentral/index.md
{{% oidc-common %}}
This example makes the following assumptions:
https://meshcentral.{{< sitevar name="domain" nojs="example.com" >}}/https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/meshcentralinsecure_secretSome of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
The following YAML configuration is an example Authelia client configuration for use with MeshCentral which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'meshcentral'
client_name: 'MeshCentral'
client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: 'two_factor'
redirect_uris:
- 'https://meshcentral.{{< sitevar name="domain" nojs="example.com" >}}/auth-oidc-callback'
scopes:
- 'openid'
- 'profile'
- 'email'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_basic'
To configure MeshCentral there is one method, using the Configuration File.
{
"domains": {
"": {
"title": "Example",
"title2": "{{< sitevar name="domain" nojs="example.com" >}}",
"authStrategies": {
"oidc": {
"issuer": "https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}",
"clientid": "meshcentral",
"clientsecret": "insecure_secret",
"newAccounts": true
}
}
}
}
}