Hi Alejandro,
I cannot find out the problem:
[oneadmin@node1 ~]$ oneuser show | grep PASSWORD
PASSWORD: 86f7e437faa5a7fce15d1ddcb9eaeaea
[oneadmin@node1 ~]$ econe-describe-instances --access-key oneadmin
--secret-key 86f7e437faa5a7fce15d
1ddcb9eaeaea
instanceId ImageId
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
hi!
#
# Auth
#
# Authentication driver for incomming requests
# - ec2, default Acess key and Secret key scheme
# - x509,
Hi,
What auth driver are you using in econe.conf?
Cheers
On 10 November 2014 09:17, Alejandro Feijóo alfei...@cesga.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Any idea where to touch... because still with the same error.
[oneadmin@test11 ~]$ oneuser show 17
USER 17
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Any idea where to touch... because still with the same error.
[oneadmin@test11 ~]$ oneuser show 17
USER 17 INFORMATION
ID : 17
NAME: alfeijooec2
GROUP : users
PASSWORD: 30e3ef7255df9b52fa130697ef83348f7ed5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Oh...
I have that 2 users.
14 alfeijoousers ldap 1 / - 1024M / -
1.0 / -
17 alfeijooec2 users core - -
-
I understant that user 14 never work in these scenario? but
That's right, if you use alfeijooec2 through ec2 you don't have to change
anything, just use the password returned by oneshow user show alfeijooec2
as AWS_SECRET_KEY
On 6 November 2014 09:23, Alejandro Feijóo alfei...@cesga.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Oh...
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi sorry for the delay... i was on vacation...
Yes that was one of the test that i did... but with the same error.
its possible any kind of problems when use ldap?
any random recomendation? :D
Thanks in advance.
El 24/10/14 10:30, Daniel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi sorry for the delay... i was on vacation...
Yes that was one of the test that i did... but with the same error.
its possible any kind of problems when use ldap?
any random recomendation? :D
Thanks in advance.
El 24/10/14 10:30, Daniel
Hi,
LDAP authentication is not supported through ec2, at least using regular
clients. If you want to use this kind of authentication you have to change
the auth method to opennebla in the econe.conf file and include the Basic
Auth headers in every ec2 request
Cheers
On 6 November 2014 08:27,
Hi,
Could you try using the password returned by oneuser show alfeijoo
Cheers
On 22 October 2014 15:57, Alejandro Feijóo alfei...@cesga.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi.
Im try to setup the econe-server at our preproduction opennebula.
After setup using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi.
Im try to setup the econe-server at our preproduction opennebula.
After setup using guide(1), im able to start service, and it seems are
ok and working.
(CODE)-
oneadmin@test ~]$ econe-server start
econe-server started
[oneadmin@test
11 matches
Mail list logo