locked
Test page with authentication is not available now ! RRS feed

  • Question

  • The error as follows, occurs in the test page of API Management which has been running without any error.

    "? An error has occurred while authorizing access via DigiPubApi Auth
     Server: invalid_client AADSTS70002: Error validating credentials.
     AADSTS50012:. Invalid client secret is provided Trace ID:
     10245afe-40f7-44b1-b5c1-ce0480edf610 Correlation ID:
     e818f892-9fbd-424d-932a-fb72625ba4d8 Timestamp: 2016-07-19 03: 20: 34Z "

    [Operation]
    1. Enter the Developer Portal as an administrator.
    2. In some API page, click "Try it" button.
    3. In "Authorization" line, select a registered authentication server which is the same Active Directory server as described in the following video.

    https://azure.microsoft.com/en-us/documentation/articles/api-management-howto-oauth2/

    Then the above error occurs.

    In the past,we could get the token of OAuth2.0 and check APIs with authentication.

    Any help and hint is most welcome.
    Thank you.

    Wednesday, July 20, 2016 10:38 AM

Answers

  • It looks like the client secret for your Azure AD application might have expired. 
    Monday, August 8, 2016 10:39 PM

All replies

  • Hello,

    Thank you for posting here!

    We are checking on the query with our backend team and would get back to you as soon as we have any updates on the same.

    I apologize for the inconvenience and appreciate your time and patience in this matter.

    Regards,

    Swikruti

    Thursday, July 21, 2016 8:25 AM
  • Thank you for your prompt reply.

    I'm looking forward to your solution.

    Thank you.

    Thursday, July 21, 2016 11:07 AM
  • Even now, we cannot test API with authentication as follows.
    How can we cope with this problem?


    •An error has occurred while authorizing access via DigiPubApi Auth Server: invalid_client AADSTS70002: Error validating credentials. AADSTS50012: Invalid client secret is provided. Trace ID: 8c0ea740-7586-4fa3-97c1-a35912ff7c3d Correlation ID: 816740cd-f4ca-4b52-8c13-bb1c2da8f6e1 Timestamp: 2016-07-27 10:53:00Z

    Wednesday, July 27, 2016 11:30 AM
  • It looks like the client secret for your Azure AD application might have expired. 
    Monday, August 8, 2016 10:39 PM
  • Thank you for your reply.
    Since there was no reply for a long time, I didn't notice the reply.
    As you say, the cause was the expiration of the authentication server.
    Thank you again.
    Saturday, October 1, 2016 8:44 AM