# \[FEATURE-13476,14109,16160\] Okta OIDC illegal\_custom\_scope

**URL:** <https://forum.inductiveautomation.com/t/feature-13476-14109-16160-okta-oidc-illegal-custom-scope/32936>\
**Category:** Ignition\
**Created:** [March 9, 2020, 6:24pm UTC](https://forum.inductiveautomation.com/t/feature-13476-14109-16160-okta-oidc-illegal-custom-scope/32936 "2020-03-09T18:24:47Z")\
**Posts on this page:** 1\
**Showing post:** 16

<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:** [July 25, 2020, 1:45am UTC](https://forum.inductiveautomation.com/t/feature-13476-14109-16160-okta-oidc-illegal-custom-scope/32936/16 "2020-07-25T01:45:45Z")

</div>

Update: we have delivered the capability to call the user info endpoint and to use the access token. There is also a perspective session prop which points to these objects. See [Added Support for OIDC User Info and Token Endpoint Response](http://forum.inductiveautomation.com/t/added-support-for-oidc-user-info-and-token-endpoint-response/37075) for more details.

---

_[View the full topic](https://forum.inductiveautomation.com/t/feature-13476-14109-16160-okta-oidc-illegal-custom-scope/32936)._