Legacy Dev Forum Posts

 View Only

Sign Up

OAuth token doesn't follow rfc6750

  • 1.  OAuth token doesn't follow rfc6750

    Posted 06-05-2025 18:24

    Cedric_Guine | 2022-11-24 20:44:24 UTC | #1

    Hi, I have a customer trying to obtain an oauth access token from Genesys on a Microsoft azure rest service by using the https://login.cac1.pure.cloud/oauth/token API.

    The API return a body with tokentype:"bearer" (b in lowercase) which doesn't comply to the rfc6750 with a B in uppercase. This causes an issue with the Microsoft Azure service which await a tokentype:"Bearer" and cannot be modify.

    Has anyone encountered this issue before?

    RFC: https://www.rfc-editor.org/rfc/rfc6750#section-4

    Regards, Cédric


    Eos_Rios | 2022-11-24 22:54:01 UTC | #2

    Note however it does follow RFC 6749 section 5.1 that 6750 replaces which explicitly states

    token_type: Required. The type of the token issued as described in Section 7.1. Value is case insensitive.

    This is a problem that creeps up in OAuth across multiple platforms and codebases.

    You may want to open a customer support case so they can work with you closely in more detail.


    Cedric_Guine | 2022-11-25 20:47:25 UTC | #3

    Thank you for the clarification @Eos_Rios, i wasn't aware of the RFC 6749 If fact, the customer support suggested me to ask my question here. I will inform my customer that they should ask Microsoft if they can adjust the expected response and hope they will.

    Cédric


    Brad_Murlin | 2022-12-06 04:51:29 UTC | #4

    Option C: Build a middleware service based on yet another platform just to handle the data relay and the difference cases of Bearer.


    system | 2023-01-06 04:52:01 UTC | #5

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 17373