Hi everyone,
I changed the username of my autodesk account from a request of autodesk directly, but unfortunately that messed up my packages ability to update them, in other words, I lost ownership of them,
Can someone have the authority to change a package username owner from an old one to a new one ?
Or at least linking the package to the E-Mail instead of the username ?
Any suggested solution ?
Greetings,
Karam
Unfortunately we can’t reassign packages from one username to another. Do you still have access to the old username enough to deprecate your old packages? The suggested method is to deprecate your old package and publish a new version with your new credentials.
We have it in our roadmap to have a more sophisticated user management system, where individuals and groups can have shared ownership of packages, as well as changes to the Package Manager UI to hide deprecated packages by default, only revealing them if someone really wants to go looking.
Hey Zach,
It is okay then, yes I do still have access to the old username,
If it is not taking so much time till this is done, the updating of user management system,
Then I can handle the updates at least from that username, and switch back to my new one,
The thing is, old users won’t know that I have left that package and uploaded a new one, therefor no updates will be delivered to them, unless i got the chance to announce it some how, so, I will keep this workaround till the user system is updated,
Thanks for the help and guidance,
Hi Zach,
Have you been able to resolve this issue ?
I just changed my username, but cannot undo since autodesk accounts cannot have an email address as a username.
Jonathan
@jacob.small Yes, I log in with the same autodesk id as before (my email), only the username has changed
I believe that one of us is understanding the issue (though your point is equally valid).
My understanding is that changes to username are caused by Autodesk account changes, and if the old name isn’t accessible then they will be unable to even access the packages to update them. It be like an employer changing your username but not your login credentials, allowing you into the system as before, but you’d have a new desktop/documents folder, and would be unable to access the old one. This sort of issue is often seen with Slack and other similar web based tools which use a SSO.
@jonathanatger can you confirm if this is your issue or if it is more along the lines of @erfajo was saying? I’ll review with the team Monday once we have a better understanding.
I’m honestly not that surprised with Autodesk, I sometimes try to find a solution for something seemingly basic in Revit and find peopl who were having the same problem a decade ago and it still hasn’t been solved.
Hi @jacob.small
My issue is just about the Autodesk account. You change your username in your account, Dynamo doesnt recognize you as the author of your package anymore.
I cannot delete it, cannot deprecate it I believe, cannot change the description, no access whatsoever. And I cannot go back to my old username. In all honesty, its my first experience with the package manager and it lasted half an hour. I decided that leaving my private email in the open (the package was maintained under my username, which was my email) wasn’t the way to go. And I’m stuck.
To the issues @erfajo is describing : I use a private account, not linked to my employer, which causes the problems mentioned. Those dont bother me too much, maybe because i am young and haven’t had time to get into those issues with job/account changes so much. I second the idea to give the possibility to link a Github account.
Other tech companies host some of their projects on Github. Why wouldn’t Autodesk let their users host their own creations on Github ?
Best regards.
@jonathanatger - the changed username is clearly an issue due to you effectively being locked out of your own account. PM me your package name, as well as the old username/email (please post neither here as that will point others to your personal info). Once I have it I’ll ask the team to remove the package entirely so that you can review how you want to share your content (I’d encourage the GitHub even if you don’t go the route of a link there for installation).