This project allows you to run configurable mock server with OpenId Connect functionality.
This is the sample of using the server in docker-compose
configuration:
version: '3'
services:
oidc-server-mock:
container_name: oidc-server-mock
image: soluto/oidc-server-mock
ports:
- "4011:80"
environment:
ASPNETCORE_ENVIRONMENT: Development
SERVER_OPTIONS_INLINE: |
{
"AccessTokenJwtType": "JWT",
"Discovery": {
"ShowKeySet": true
}
}
API_SCOPES_INLINE: |
[
{
"Name": "some-app-scope-1"
},
{
"Name": "some-app-scope-2"
}
]
API_RESOURCES_INLINE: |
[
{
"Name": "some-app",
"Scopes": ["some-app-scope-1", "some-app-scope-2"]
}
]
USERS_CONFIGURATION_INLINE: |
[
{
"SubjectId":"1",
"Username":"User1",
"Password":"pwd",
"Claims": [
{
"Type": "name",
"Value": "Sam Tailor"
},
{
"Type": "email",
"Value": "[email protected]"
},
{
"Type": "some-api-resource-claim",
"Value": "Sam's Api Resource Custom Claim"
},
{
"Type": "some-api-scope-claim",
"Value": "Sam's Api Scope Custom Claim"
},
{
"Type": "some-identity-resource-claim",
"Value": "Sam's Identity Resource Custom Claim"
}
]
}
]
CLIENTS_CONFIGURATION_PATH: /tmp/config/clients-config.json
volumes:
- .:/tmp/config:ro
When clients-config.json
is as following:
[{
"ClientId": "implicit-mock-client",
"Description": "Client for implicit flow",
"AllowedGrantTypes": [
"implicit"
],
"AllowAccessTokensViaBrowser": true,
"RedirectUris": [
"http://localhost:3000/auth/oidc",
"http://localhost:4004/auth/oidc"
],
"AllowedScopes": [
"openid",
"profile",
"email"
],
"IdentityTokenLifetime": 3600,
"AccessTokenLifetime": 3600
},
{
"ClientId": "client-credentials-mock-client",
"ClientSecrets": [
"client-credentials-mock-client-secret"
],
"Description": "Client for client credentials flow",
"AllowedGrantTypes": [
"client_credentials"
],
"AllowedScopes": [
"some-app"
],
"ClientClaimsPrefix": "",
"Claims": [
{
"Type": "string_claim",
"Value": "string_claim_value"
},
{
"Type": "json_claim",
"Value": "['value1', 'value2']",
"ValueType": "json"
}
]
}
]
Clients configuration should be provided. Test user configuration is optional (used for implicit flow only).
There are two ways to provide configuration for supported scopes, clients and users. You can either provide it inline as environment variable:
-
SERVER_OPTIONS_INLINE
-
API_SCOPES_INLINE
-
USERS_CONFIGURATION_INLINE
-
CLIENTS_CONFIGURATION_INLINE
-
API_RESOURCES_INLINE
-
IDENTITY_RESOURCES_INLINE
or mount volume and provide the path to configuration json as environment variable:
-
SERVER_OPTIONS_PATH
-
API_SCOPES_PATH
-
USERS_CONFIGURATION_PATH
-
CLIENTS_CONFIGURATION_PATH
-
API_RESOURCES_PATH
-
IDENTITY_RESOURCES_PATH
To use https
protocol with the server just add the following environment variables to the docker run
/docker-compose up
command, expose ports and mount volume containing the pfx file:
environment:
ASPNETCORE_URLS: https://+:443;http://+:80
ASPNETCORE_Kestrel__Certificates__Default__Password: <password for pfx file>
ASPNETCORE_Kestrel__Certificates__Default__Path: /path/to/pfx/file
volumes:
- ./local/path/to/pfx/file:/path/to/pfx/file:ro
ports:
- 8080:80
- 8443:443
Since Aug 2020 Chrome has a new secure-by-default model for cookies, enabled by a new cookie classification system. Other browsers will join in near future.
There are two ways to use oidc-server-mock
with this change.
- Run the container with HTTP enables (see above).
- Change cookies
SameSite
mode from defaultNone
toLax
. To do so just add the following toSERVER_OPTIONS_INLINE/PATH
env var:
{
"Authentication": {
"CookieSameSiteMode": "Lax",
"CheckSessionCookieSameSiteMode": "Lax"
}
}
-
Clone the repo:
git clone [email protected]:Soluto/oidc-server-mock.git
-
Install
npm
packages (run from/e2e
folder):npm install
Note: During the build of Docker image UI source code is fetched from github. If you experience some issues on project compile step of Docker build or on runtime try to change the branch or commit in the script.
-
Run tests:
npm run test