# \[BUG-12277\] OpenID to Microsoft Azure

**URL:** <https://forum.inductiveautomation.com/t/bug-12277-openid-to-microsoft-azure/21745>\
**Category:** Ignition Early Access\
**Created:** [January 8, 2019, 4:55pm UTC](https://forum.inductiveautomation.com/t/bug-12277-openid-to-microsoft-azure/21745 "2019-01-08T16:55:16Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [January 11, 2019, 8:38pm UTC](https://forum.inductiveautomation.com/t/bug-12277-openid-to-microsoft-azure/21745/7 "2019-01-11T20:38:47Z")

</div>

Which browser are you using? Do you get the same exception if you try logging in from a private window?

I did not alter the default user attribute mapping for an OIDC IdP, which is a direct mapping to ‘sub’ for ID and username and no mapping configured for the other attributes.

Here are the steps I took to setup AAD as an OP for Ignition:  
[How to set up Azure Active Directory as an OpenID Connect Provider for Ignition.pdf](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/fcc18f168199f7ae581e4855677b00f22890b020.pdf) (2.7 MB)

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-12277-openid-to-microsoft-azure/21745)._