From 74826c409e3da71c1107f349ed79d03d60e6999a Mon Sep 17 00:00:00 2001 From: Simon Bein Date: Fri, 27 Sep 2024 13:39:42 +0200 Subject: [PATCH 1/3] Add serving info for builtin connector Signed-off-by: Simon Bein --- content/docs/connectors/local.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/connectors/local.md b/content/docs/connectors/local.md index 5db1c52..1310ed7 100644 --- a/content/docs/connectors/local.md +++ b/content/docs/connectors/local.md @@ -52,6 +52,8 @@ Both local users and password grants are enabled, allowing the exchange of a tok ```yaml issuer: http://localhost:8080/dex +web: + http: 127.0.0.1:8080 storage: # .. storage configuration # Setup clients staticClients: From 32fe9f20fe64c4f1088b2ae6387cfb571bec048c Mon Sep 17 00:00:00 2001 From: Simon Bein Date: Fri, 27 Sep 2024 13:41:55 +0200 Subject: [PATCH 2/3] Add note on user storage for users created via configuration file Signed-off-by: Simon Bein --- content/docs/connectors/local.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/connectors/local.md b/content/docs/connectors/local.md index 1310ed7..287268a 100644 --- a/content/docs/connectors/local.md +++ b/content/docs/connectors/local.md @@ -40,6 +40,7 @@ To specify users within the configuration file, the `staticPasswords` option can * `username`: The username associated with the user. * `userID`: The unique identifier (ID) of the user. +Users created via the configuration file are stored only in memory and not in the underlying configured storage. #### Dynamic configuration (API) Users can be dynamically managed via the gRPC API, offering a versatile method to handle user-related operations within the system. From 128a6f66ef3b68bc503751aa461af44d7970c4ca Mon Sep 17 00:00:00 2001 From: Simon Bein Date: Fri, 27 Sep 2024 13:47:29 +0200 Subject: [PATCH 3/3] Fix curl examples in builtin connector Signed-off-by: Simon Bein --- content/docs/connectors/local.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/content/docs/connectors/local.md b/content/docs/connectors/local.md index 287268a..6e954ae 100644 --- a/content/docs/connectors/local.md +++ b/content/docs/connectors/local.md @@ -86,24 +86,26 @@ oauth2: Depending on whether you use a public or a private client you need to either include the just `clientId` or the `clientId` and `clientPassword` in the authorization header. **Public Client** + ```shell curl -L -X POST 'http://localhost:8080/dex/token' \ --H 'Authorization: Basic cHVibGljLWNsaWVudAo=' \ # base64 encoded: public-client -H 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'grant_type=password' \ --data-urlencode 'scope=openid profile' \ --data-urlencode 'username=admin@example.com' \ ---data-urlencode 'password=admin' +--data-urlencode 'password=password' \ +--data-urlencode 'client_id=public-client' ``` - **Private Client** + ```shell curl -L -X POST 'http://localhost:8080/dex/token' \ --H 'Authorization: Basic cHJpdmF0ZS1jbGllbnQ6YXBwLXNlY3JldAo=' \ # base64 encoded: private-client:app-secret -H 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'grant_type=password' \ --data-urlencode 'scope=openid' \ --data-urlencode 'username=admin@example.com' \ ---data-urlencode 'password=admin' +--data-urlencode 'password=password' \ +--data-urlencode 'client_id=private-client' \ +--data-urlencode 'client_secret=app-secret' ```