UNSOLVED

elSane

updated

12 years ago

E

elSane

2 Posts

0

1822

May 3rd, 2015 13:00

Avamar API credential issues

2015-05-03 19:38:39,661|WARN |syncScheduler-1|org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl|HHH000387: ResultSet's statement was not registered

2015-05-03 19:38:48,556|DEBUG|http-nio-8543-exec-6|com.emc.concerto.web.filter.MyBasicAuthenticationFilter|Basic Authentication Authorization header found for user 'customUser'

2015-05-03 19:38:48,562|DEBUG|http-nio-8543-exec-6|com.emc.concerto.web.filter.MyBasicAuthenticationFilter|Authentication request for failed: org.springframework.security.authentication.BadCredentialsException: Bad credentials

I edit the config files as stated in the API guide:

  • /usr/local/avamar/bin/restserver.sh --stop
  • vim /usr/local/avamar/var/rest-api/server_data/restserver.properties
    • provider.user=customUser
    • provider.password=customPass
  • /usr/local/avamar/bin/restserver.sh --start


After starting the restserver, the 'provider.password' value is replaced with 'ENC(encryptedString)'; however, any attempt to authenticate with those credentials fails, either through '/usr/local/avamar/bin/restCLI.pl' or using a perl script to make the rest calls.

Any suggestions on what can be done to set up usable credentials?  The only troubleshooting suggestion in the API guide is to validate the rest-api database exists in psl.  I have been able to connect to the database as described in the guide.

  • 748

    0

    Posted March 13th, 2017 13:00

    Did you ever find a fix for this? I'm running into the same issue.

  • Timothy4

    1 Rookie

    •

    27 Posts

    749

    0

    Posted April 7th, 2017 13:00

    I'm having the same problem, identical steps as the OP. We just got the API installed on our test AVE, followed the change user and password procedure, can't get valid auth through any client (restCLI.pl, Google Postman, or direct through PHP). always gives me a 401.

    the fix is: "don't change the user"

    I changed the username back to just "admin" from the "restadmin" we had changed it to; and I could auth fine after doing that.

  • ionthegeek

    2 Intern

    •

    2049 Posts

    748

    2

    Posted April 11th, 2017 14:00

    I had a chat with the developers. This is Bug 271032 and it is fixed in the 7.4 release of the API.

  • 748

    0

    Posted April 16th, 2017 06:00

    i have same error, did you resolve this problem?