Full upgrade (#19)
- SecretName is now mandatory - One can update client_secret in Hydra by creating new Secret object and changing the SecretName in CR instance
This commit is contained in:
committed by
Tomasz Smelcerz
parent
8009fd63d3
commit
294c171ac6
@ -13,4 +13,5 @@ spec:
|
||||
- id_token
|
||||
- code
|
||||
- token
|
||||
scope: "read write"
|
||||
scope: "read write"
|
||||
secretName: my-secret-123
|
||||
|
@ -0,0 +1,27 @@
|
||||
apiVersion: v1
|
||||
kind: Secret
|
||||
metadata:
|
||||
name: my-secret-456
|
||||
namespace: default
|
||||
type: Opaque
|
||||
data:
|
||||
client_id: MDA5MDA5MDA=
|
||||
client_secret: czNjUjM3cDRzc1ZWMHJEMTIzNA==
|
||||
---
|
||||
apiVersion: hydra.ory.sh/v1alpha1
|
||||
kind: OAuth2Client
|
||||
metadata:
|
||||
name: my-oauth2-client-2
|
||||
namespace: default
|
||||
spec:
|
||||
grantTypes:
|
||||
- client_credentials
|
||||
- implicit
|
||||
- authorization_code
|
||||
- refresh_token
|
||||
responseTypes:
|
||||
- id_token
|
||||
- code
|
||||
- token
|
||||
scope: "read write"
|
||||
secretName: my-secret-456
|
Reference in New Issue
Block a user