This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[acc 3.00]Unable to login to Gateway manager

Hi All

I am using the Amazon EC2 with ACC 3.00 and I am unable to login to gateway manager using my own license (I've created via portal). My ASG device connected to ACC andI am able to login to ACC. For some reason I can't access the Gateway Manager. Group and users are correctly set on my ACC.

It seems (reading the forums) that the problem is not appearing when using the beta license (any idea where to get it?)

Thanks

This thread was automatically locked due to age.

Parents

0 wingman over 13 years ago

Hakan Unfortunately this didn't work. I've created a user and then executed the command. same result. I then restart the processes and executed the command-same result
Cancel
Vote Up 0 Vote Down

Cancel
0 Hakan Yueksel over 13 years ago in reply to wingman
Ok, I have also experienced the case that the first attempt with this
trick didn't help but restarting the daemons several times and trying
again helped.

However, as this is a timing problem and timing is different amongst
different machines I can imagine that the timing conditions on your
machine are quite disadvantageous for the workaround.

There is also the possibility to put the user manually into the acc
database, but please be careful:

[LIST=1]
find out the ref string for your admin:
cc get accd access allowed_admins

login into the database:
psql -U acc

invoke following insert in the prompt of psql:
insert into user_info (guid, data) values ('REF_DefaultSuperAdmin', '{"name":"admin","type":"user"}');

quit the database:
\q

restart acc daemon
/var/mdw/scripts/accd restart

[/LIST]

Regards, Hakan
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Hakan Yueksel over 13 years ago in reply to wingman
Ok, I have also experienced the case that the first attempt with this
trick didn't help but restarting the daemons several times and trying
again helped.

However, as this is a timing problem and timing is different amongst
different machines I can imagine that the timing conditions on your
machine are quite disadvantageous for the workaround.

There is also the possibility to put the user manually into the acc
database, but please be careful:

[LIST=1]
find out the ref string for your admin:
cc get accd access allowed_admins

login into the database:
psql -U acc

invoke following insert in the prompt of psql:
insert into user_info (guid, data) values ('REF_DefaultSuperAdmin', '{"name":"admin","type":"user"}');

quit the database:
\q

restart acc daemon
/var/mdw/scripts/accd restart

[/LIST]

Regards, Hakan
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data