Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can we replace the deprecated SHA-1 algorithm for generating open-api token? #4503

Closed
mghio opened this issue Aug 7, 2022 · 1 comment · Fixed by #4504
Closed

Can we replace the deprecated SHA-1 algorithm for generating open-api token? #4503

mghio opened this issue Aug 7, 2022 · 1 comment · Fixed by #4504

Comments

@mghio
Copy link
Contributor

mghio commented Aug 7, 2022

Is your feature request related to a problem? Please describe.
Can we replace the deprecated SHA-1 algorithm for generating open-api tokens in ConsumerService.

image

Describe the solution you'd like
e.g. Change to sha256 sha256 to generate open-api token.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
see sha-1, sha256.

@nobodyiam
Copy link
Member

I think we can do that, as the algorithm is only used when generating the token, so it should have no side effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants