none
Unauthorized error connecting to Azure Config Service RRS feed

  • Question

  • Hi,

    I'm tring to connect Azure Config Service (trial account) using a java application through spring-cloud-azure-appconfiguration-config following the official

    But after configuring the service I get this error:

    java.lang.IllegalStateException: Failed to load keys from Azure Config Service. With status code: 401, response: HttpResponseProxy{HTTP/1.1 401 Unauthorized [Server: nginx/1.13.9, Date: Fri, 26 Apr 2019 07:57:55 GMT, Content-Length: 0, Connection: keep-alive, WWW-Authenticate: HMAC-SHA256 error="invalid_token", error_description="Invalid access token date", x-ms-request-id: 65a517c5-0ee8-43a4-bba9-caf00c5c58d2, x-ms-correlation-request-id: 65a517c5-0ee8-43a4-bba9-caf00c5c58d2, Strict-Transport-Security: max-age=15724800; includeSubDomains;] [Content-Length: 0,Chunked: false]}
    	at com.microsoft.azure.spring.cloud.config.ConfigServiceTemplate.getRawResponse(ConfigServiceTemplate.java:200) ~[spring-cloud-azure-appconfiguration-config-1.1.0.M3.jar:1.1.0.M3]]

    I've tried providing all the available key strings for the property below:

    spring.cloud.azure.appconfiguration.stores[0].connection-string

    What am I missing?

    Thanks in advance

    • Edited by user872 Friday, April 26, 2019 8:27 AM
    Friday, April 26, 2019 8:27 AM

Answers

  • Hi,

    thanks for reply and apologize me too

    Yes issue was related to a time issue because my java application generated date in a not expected manner

    In my case I solved applying a different

    user.language
    system property because the underlying code apply a conversion based on such value

    Hope this helps too ;)

    • Edited by user872 Thursday, August 1, 2019 1:11 PM
    • Marked as answer by user872 Thursday, August 1, 2019 1:11 PM
    Thursday, August 1, 2019 1:10 PM

All replies

  • Hi ,

    Thanks for raising this issue. I will investigate and update here.

    Friday, April 26, 2019 12:10 PM
    Moderator
  • Hi,

    Apologies for delay.

    Please make sure the computer time is accurate (less than 15 minutes off). The REST API doc has a bit details.

    Date

    Date and Time at which the request was originated. It can not be more than 15 min off from current GMT. The value is an HTTP-date, as described in section 3.3.1

    Hope this helps!

    Monday, May 6, 2019 9:50 AM
    Moderator
  • Hi,

    thanks for reply and apologize me too

    Yes issue was related to a time issue because my java application generated date in a not expected manner

    In my case I solved applying a different

    user.language
    system property because the underlying code apply a conversion based on such value

    Hope this helps too ;)

    • Edited by user872 Thursday, August 1, 2019 1:11 PM
    • Marked as answer by user872 Thursday, August 1, 2019 1:11 PM
    Thursday, August 1, 2019 1:10 PM