Customer bearer token prefix

  • Hi,
    first, let me thank you for such a wonderful plug-in, it is really well though out and easy to use.
    My backend uses a different prefix for the authentication headers, which is “Token: XXXXX” instead of “Bearer: XXXXX”. As such, after configuring my authentication scheme in the plug-in, the back-end returns a 403.
    Would it be possible to extend the authentication section of the plug-in to support custom prefixes? Perhaps a new field in the form?
    That would be awesome and add a lot of flexibility to this plug-in.

    -raz

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Ironikus

    (@ironikus)

    Hi @razique – thank you very much for your message, as well as for using our plugin!
    I just talked with my team and we will implement that within the next version launch.
    I’ll keep you updated here! ??

    Thread Starter Raz

    (@razique)

    Hi @ironikus I do see the new feature ??
    Thank you so much, that is awesome, and will make my life easier ??
    I will do some more testing and will get back to you if there’s any issue.

    Have a nice day.

    Plugin Contributor Ironikus

    (@ironikus)

    Hey @razique – Thank you for coming back to me, I hope it all worked out for you.
    In case you do not have further questions, feel free to close the topic as well. ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Customer bearer token prefix’ is closed to new replies.