# Authorization Problem

**URL:** <https://forum.opennebula.io/t/authorization-problem/704>\
**Category:** Product Support\
**Created:** [May 7, 2015, 1:48pm UTC](https://forum.opennebula.io/t/authorization-problem/704 "2015-05-07T13:48:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kpatron](https://avatars.discourse-cdn.com/v4/letter/k/e47c2d/32.png) [@kpatron](https://forum.opennebula.io/u/kpatron)\
**Post date:** [May 7, 2015, 1:48pm UTC](https://forum.opennebula.io/t/authorization-problem/704/1 "2015-05-07T13:48:00Z")

</div>

Hello Guys:

It’s me again with a huge problem. So I was testing a few things with users and changed by mistake the authorization of oneadmin from core to server\_cipher when I was going to actually change the serveradmin user.  
Is there any way to correct this or should I reinstall the whole thing? It is because I cannot do any OpenNebula commands.  
I changed the serveradmin to core in a hope that it will enter the Sunstone GUI but without success so I decided to revert but instead did what I did. Can this core change help in any way?

Best regards, hope that you can help me soon.

---

<div class="post-metadata">

**Author:** ![kpatron](https://avatars.discourse-cdn.com/v4/letter/k/e47c2d/32.png) [@kpatron](https://forum.opennebula.io/u/kpatron)\
**Post date:** [May 7, 2015, 2:37pm UTC](https://forum.opennebula.io/t/authorization-problem/704/2 "2015-05-07T14:37:08Z")

</div>

Well…

I have done the following with success, so you can close this problem:

- Since I changed the serveradmin to core, it seemed the one chance to correct everything so… I created a new user in my machine with the name serveradmin
- Then I logged in the serveradmin account and created the directory .one by issuing **$ mkdir .one**
- I finally changed to that directory and created a file that contained serveradmin:my\_password and saved evrything
- I performed a check with **oneuser show** and **oneuser list** and seemed to work, so I finally performed **oneuser chauth oneadmin core**
- Logged in the oneadmin account and performed all of the different one commands to check. WORKS!

Thanks, hope this can help other people that like me do this mistake.
