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
improvement: support user-auth local dev kratos (#62)
kratos redirect URLs are driven by config and are static,
this will allow spining up another instance of user_auth(kratos) without
oathkeeper, and allow the cookies to be sent cross-site
127.0.0.1:3000 -> backend on the cloud (for dev-env)
allow modifying scheme allowing dev-instance of kratos with localhost
Copy file name to clipboardExpand all lines: modules/user_auth/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,9 +35,11 @@ No requirements.
35
35
| backend\_service\_domain | Domain of the backend service |`string`| n/a | yes |
36
36
| cookie\_signing\_secret\_key | Default secret key for signing cookies |`string`| n/a | yes |
37
37
| create\_namespace | Whether to create the auth namespace(defaults to true), otherwise just references the namespace |`bool`|`true`| no |
38
+
| disable\_oathkeeper | To not provision Oathkeeper, this is useful when you want multiple Kratos setup, while only 1 Oathkeeper proxy to route to them, for example sharing Oathkeeper between a Dev and Staging Kratos |`bool`|`false`| no |
38
39
| external\_secret\_backend | The backend external-secrets will pull secret data from to create a corresponding secret in kubernetes. If empty, external-secrets will not be used. You'll need to make sure the secret is created manually. |`string`|`"secretsManager"`| no |
39
40
| external\_secret\_name | Name of a secret in an external secrets backend that contains the content to pull into a kubernetes secret for Kratos to use |`string`| n/a | yes |
40
41
| frontend\_service\_domain | Domain of the frontend |`string`| n/a | yes |
42
+
| frontend\_use\_https | Whether frontend URLs should be https, unless your developing locally you should leave the default as is. |`bool`|`true`| no |
41
43
| jwks\_content | The content of a JWKS file for Oathkeeper |`string`| n/a | yes |
42
44
| k8s\_local\_exec\_context | Custom resource (Oathkeeper Rules are created using local-exec with kubectl), if not specified it will target your current context from kubeconfig |`string`|`""`| no |
43
45
| kratos\_default\_redirect\_ui\_path | Setting the default path after self-service flows(login/signup/verify/settings), kratos will redirect you to frontend |`string`|`"/dashboard"`| no |
description="To not provision Oathkeeper, this is useful when you want multiple Kratos setup, while only 1 Oathkeeper proxy to route to them, for example sharing Oathkeeper between a Dev and Staging Kratos"
99
+
type=bool
100
+
default=false
101
+
}
102
+
103
+
variable"frontend_use_https" {
104
+
description="Whether frontend URLs should be https, unless your developing locally you should leave the default as is."
0 commit comments