the issue still exist,
any news on this specific topic? I’m trying since yesterday.
I am also having the same issue on win11 and ubuntu. And found that this error occurs only when DUID is added. When I tried to generate without DUID the certificate was generated with warning.
It is working for me now. Seems like the issue has been fixed.
2 Likes
i confirm, it is working now
1 Like
Problem has been fixed. Please check
Everything works as predicted.
not working now error 401
1 Like
Getting Error 401 as well. Windows 10, Tizen Studio 6.1, Certificate Manager updated
2 Likes
Getting the same error (401). Win 11, Tizen Studio 6.1, Certificate Manager
1 Like
Getting error 401 too, tried reinstalling tizen studio and restarting machine but neither worked. Win 11, Tizen Studio 6.1, Certificate manager
2 Likes
Certificate manager, Generation Failed “Server response code: 401“, Win 10, Tizen Studio 6.1
1 Like
Hello,
Apologies for the inconvenience.
We would like to request all of you to make sure your Tizen Studio and Certificate manager is up to dated. In the latest version of Certificate manager which is 2.0.71 should not face the same issue.
Let us know the status.
Thanks
Shamima
Samsung Developer Program team
Today I downloaded Tizen Studio 6.1 from the site, and I believe it is the latest version, but unfortunately the certificate does not work.
Thank you for your answer Shamima!
The Certificate Manager is 2.0.71, as shown in the Package manager. Studio is 6.1
Although I don’t know if it may be relative, but maybe the issue lies in the authorization? During certificate creation, on the step where the browser opens and we need to enter credentials - right after it shows the message “Login Successful. Please continue on the Certificate Manager UI” - the Error 401 pops up in the Certificate Manager GUI. But, at the same time, I receive a message on my Samsung Galaxy phone, where it says “There was a login attempt, was it you?” And there’s the options yes/no. May the error be related to security/confirmation issues? Just a hunch…
Edit: Also, prior to Installing Studio 6.1 - I had a separate version 6.0 installed in another folder on the drive. I didn’t delete that one yet. Not sure if that may cause some conflict. Will try to do a complete wipe of all the software and try again later…
Same issue here. I am on Version 2.0.71. Please escalate to engineering team. Across my team all 5 developers have this issue. It is impacting 100% of your developers.