You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients configuration should be provided. Test user configuration is optional (used for implicit flow only).
225
-
226
-
There are two ways to provide configuration for supported scopes, clients and users. You can either provide it inline as environment variable:
227
-
228
-
- `SERVER_OPTIONS_INLINE`
229
-
- `LOGIN_OPTIONS_INLINE`
230
-
- `LOGOUT_OPTIONS_INLINE`
231
-
- `API_SCOPES_INLINE`
232
-
- `USERS_CONFIGURATION_INLINE`
233
-
- `CLIENTS_CONFIGURATION_INLINE`
234
-
- `API_RESOURCES_INLINE`
235
-
- `IDENTITY_RESOURCES_INLINE`
236
-
237
-
or mount volume and provide the path to configuration json as environment variable:
238
-
239
-
- `SERVER_OPTIONS_PATH`
240
-
- `LOGIN_OPTIONS_PATH`
241
-
- `LOGOUT_OPTIONS_PATH`
242
-
- `API_SCOPES_PATH`
243
-
- `USERS_CONFIGURATION_PATH`
244
-
- `CLIENTS_CONFIGURATION_PATH`
245
-
- `API_RESOURCES_PATH`
246
-
- `IDENTITY_RESOURCES_PATH`
247
-
248
-
The configuration format can be Yaml or JSON both for inline or file path options.
249
-
250
-
In order to be able to override standard identity resources set `OVERRIDE_STANDARD_IDENTITY_RESOURCES` env var to `True`.
251
-
252
-
## Base path
253
-
254
-
The server can be configured to run with base path. So all the server endpoints will be also available with some prefix segment.
255
-
For example `http://localhost:8080/my-base-path/.well-known/openid-configuration` and `http://localhost:8080/my-base-path/connect/token`.
256
-
Just set `BasePath` property in `ASPNET_SERVICES_OPTIONS_INLINE/PATH` env var.
257
-
258
-
## Custom endpoints
259
-
260
-
### User management
261
-
262
-
Users can be added (in future also removed and altered) via `user management` endpoint.
263
-
264
-
- Create new user: `POST`request to `/api/v1/user` path.
265
-
The request body should be the `User` object. Just as in `USERS_CONFIGURATION`.
266
-
The response is subjectId as sent in request.
267
-
268
-
- Get user: `GET`request to `/api/v1/user/{subjectId}` path.
269
-
The response is `User` object
270
-
271
-
- Update user `PUT` request to `/api/v1/user` path. (**Not implemented yet**)
272
-
The request body should be the `User` object. Just as in `USERS_CONFIGURATION`.
273
-
The response is subjectId as sent in request.
274
-
275
-
> If user doesn't exits it will be created.
276
-
277
-
- Delete user: `DELETE`request to `/api/v1/user/{subjectId}` path. (**Not implemented yet**)
278
-
The response is `User` object
279
-
280
-
## HTTPS
281
-
282
-
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:
283
-
284
-
```yaml
285
-
environment:
286
-
ASPNETCORE_URLS: https://+:443;http://+:80
287
-
ASPNETCORE_Kestrel__Certificates__Default__Password: <password for pfx file>
Since Aug 2020 Chrome has a new [secure-by-default model](https://blog.chromium.org/2019/10/developers-get-ready-for-new.html) for cookies, enabled by a new cookie classification system. Other browsers will join in near future.
17
+
Usage guide can be found [upstream](https://github.com/Soluto/oidc-server-mock?tab=readme-ov-file).
301
18
302
-
There are two ways to use `oidc-server-mock` with this change.
19
+
## Installation
20
+
[Installation guide for the latest release](https://github.com/xdev-software/oidc-server-mock/releases/latest#Installation)
303
21
304
-
1. Run the container with HTTPS enabled (see above).
305
-
2. Change cookies `SameSite` mode from default `None` to `Lax`. To do so just add the following to `SERVER_OPTIONS_INLINE` (or the file at `SERVER_OPTIONS_PATH`):
If you need support as soon as possible and you can't wait for any pull request, feel free to use [our support](https://xdev.software/en/services/support).
0 commit comments