Webinar (on-demand): OutSystems and Analytics Integration: A New Strategy to Reduce Costs

Discover everything you need to know about Hubway Connect

Try the product online without any installation or purchase commitment
Hubway Connect

Innovative ways to leverage your data for business outcomes

Find out how Hubway Connect can help you get more value from your OutSystems platform
Hubway Connect

Learn and expand your Hubway Connect knowledge

Deep dive in articles, videos and technical information to maximise its use
Hubway Connect

Start free and expand without surprises

Choose the Hubway Connect offer that best meets your needs and suits your budget
Hubway Connect

We are here to help. Let’s talk.

Connect with us via your preferred channel and we will be happy to answer your questions
Hubway Connect
  1. Home
  2. Knowledge Base
  3. FAQs
  4. Authentication
  5. Handle header parameters when using custom authentication

Handle header parameters when using custom authentication

When using any type of custom authentication in runtime, for example to support OAuth2 authentication mechanism, make sure the Authentication Type is correctly set in the Authorization header parameters.

For instance, when using Postman for API testing, go to the Authorization Tab, and set:

  • Authentication Type with ‘Bearer Token’
  • Token as your own token provided by your identity provider

Handle header parameters when using custom authentication

 

The default authentication type in any browser is Basic Credentials / Basic Authentication, so a custom authentication will not work when invoking OData services through the browser.

If you find issues connecting to your API using Custom Authentication reach out to the product support team.

Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support