2
By accessing Jasmin Nitrogen and upgrading a Credentials Client-type authorization system it is not possible to regenerate the client secret. There is currently an error that secret there is no.
The fact that the application is published has some relevance in this operation?
[EDIT 2019/04/17]
The error that appears to me is the following:
0
This problem is being analyzed, it is actually a product anomaly. To circumvent it may generate a new application and client secret.
If you want to keep the application id and generate new client secret can contact me through SPRING (for security reasons).
Thank you Jorge. I would only ask that once the product anomaly was resolved to mention in this post for historical purposes if someone has the same problem.
0
Hello John yes you can reset the client secret, as you can see in the image below.
Thanks Sergio. The problem I have is exactly when I use this option. I updated the original post with the Nitrogen response.
Browser other questions tagged api oauth2 oauth
You are not signed in. Login or sign up in order to post.
Hello John. This problem has already been solved. Thank you.
– Hugo Quintela Ribeiro