Integration Gateway Authentication
Succeed Insurance plans on making Integration Gateway its primary integration hub. Because of that, they need to understand how authentication is managed with Integration Gateway.
Learning Objectives
The learning objectives for this module are:
- Understand how authentication is performed by inbound callers to Integration Gateway.
- Understand to configure authentication for inbound callers to Integration Gateway.
- Understand how authentication is performed by outbound callers to Integration Gateway.
- Understand how to configure Integration Gateway to call an external service link a Cloud API.
Inbound REST API authentication
Integration Gateway (IG) controls access to its applications and data by authenticating and authorizing the inbound API callers. Authentication is the process of verifying that the caller is who they claim to be. Authorization is the process of determining what operations and data the caller is allowed to access.
Basic authentication
This is the most straightforward method and the easiest. With this method, the sender places a username:password into the request header. The username and password are encoded with Base64, which is an encoding technique that converts the username and password into a set of 64 characters to ensure safe transmission.
OAuth2 authentication
OAuth relies on authentication scenarios called flows, which allow the resource owner (user) to share the protected content from the resource server without sharing their credentials. For that purpose, an OAuth 2.0 server issues access tokens that the client applications can use to access protected resources on behalf of the resource owner.
Configuring REST API authentication
To to understand how to configure REST API authentication for IG, check out this Guidewire documentation.
Outbound REST API authentication
Integration apps make outbound HTTP calls to external services to implement business logic. There are two main types of external services that Integration Gateway apps communicate with:
- Third-party services - Typically integration apps use Web API messaging interfaces such as customer message brokers and file exchange
Integration Gateway supports OAuth and mutual Transport Layer Security (mTLS) to authenticate outbound API calls to third-party services. The mTLS authentication is implemented by Guidewire Cloud Console.
- InsuranceSuite applications - Integration apps make calls to Cloud API, or REST API endpoints to access the data or trigger actions within the applications. When an integration app tries to access data or execute an action, the caller must be authenticated and authorized.
For more information on how to perform how to perform authentication to an InsuranceSuite application, check out this documentation.
Knowledge Check
To validate your knowledge please complete this Knowledge Check of the information you just read.
Was this page helpful?