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
When I run the CLI command to get JWKS the response comes back with an empty set attribute. The expected behavior is that the set attribute should contain the JWKS name like so "set": "my-ory-key-set". The same behavior is seen whether you pass no --format argument or you pass --format with a valid format type.
Reproducing the bug
Steps to reproduce:
Create a JWK using the API or CLI - ory create jwk my-ory-key-set --alg ES256
Run ory get jwk my-ory-key-set [--format table|yaml|json|json-pretty|...
See the result contains a set attribute/column but it has an empty string value instead of "my-ory-key-set"
Relevant log output
No response
Relevant configuration
No response
Version
v0.3.4
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
Ory Network
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Ory Network Project
https://pensive-lalande-5xnn9nb8fm.projects.oryapis.com
Describe the bug
When I run the CLI command to get JWKS the response comes back with an empty
set
attribute. The expected behavior is that the set attribute should contain the JWKS name like so"set": "my-ory-key-set"
. The same behavior is seen whether you pass no--format
argument or you pass--format
with a valid format type.Reproducing the bug
Steps to reproduce:
ory create jwk my-ory-key-set --alg ES256
ory get jwk my-ory-key-set [--format table|yaml|json|json-pretty|...
set
attribute/column but it has an empty string value instead of"my-ory-key-set"
Relevant log output
No response
Relevant configuration
No response
Version
v0.3.4
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
Ory Network
Additional Context
No response
The text was updated successfully, but these errors were encountered: