Authentication requirements for Widgets
This article outlines the authentication pre-requisites, to build an Igloo widget that will connect and authenticate to your proprietary and/or 3rd-party software or system.
Warning: Authentication like this is only supported within the Integrations Widget framework.
All that is required on the Igloo side is to Sign-Up for the Developer Program, and Verify the configuration of your Igloo-provided Azure instance.
OAuth must be configured in your corporate environment/greater IT solution prior to building an Igloo widget that will utilize the protocol to authenticate to your 3rd-party system.
Note: To save time, please make sure that all of these 3rd-party requirements are met 100% before attempting to build anything on the Igloo side.
Igloo uses 3rd-party OAuth tokens, and does not issue tokens.
Both Authorization and Implicit flow are supported, but only Authorization flow is recommended because it doesn’t involve whitelisting IPs and is therefore a more scalable approach to widget design.
Follow this guide to learn how to configure and implement OAuth on the front-end of a web browser. This resource will help you implement OAuth in your Igloo widget after making the appropriate server-side configuration changes (assuming you are not configured for OAuth in your corporate environment/greater IT solution already.)
The OAuth Community Site is the greatest online resource for OAuth 2.0 information.
Tip: Full client and server side walkthroughs are available for OAuth implementation at the above link.