# Does Chronograf work with Okta oauth?

**URL:** <https://community.influxdata.com/t/does-chronograf-work-with-okta-oauth/3892>\
**Category:** Dashboards\
**Created:** [February 5, 2018, 7:11pm UTC](https://community.influxdata.com/t/does-chronograf-work-with-okta-oauth/3892 "2018-02-05T19:11:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hien](https://avatars.discourse-cdn.com/v4/letter/h/858c86/32.png) [@hien](https://community.influxdata.com/u/hien)\
**Post date:** [February 5, 2018, 7:11pm UTC](https://community.influxdata.com/t/does-chronograf-work-with-okta-oauth/3892/1 "2018-02-05T19:11:15Z")

</div>

Has anyone gotten Chronograf working with Okta for oauth? I’m currently using generic oauth settings, but I keep getting the following error message on Okta when I try to login:

 ![30%20AM](https://us1.discourse-cdn.com/flex023/uploads/influxdata/original/1X/df390fd97b46c442afbabc1dfb48a50e0e818927.png)

current version of Chronograf: 1.4.0-1

On the Okta side, I created a Web OpenID connect app and used the following:  
Allowed grant types: Authorization Code  
login redirect URIs: [http://35.x.x.x:8888/oauth/generic/callback](http://35.x.x.x:8888/oauth/generic/callback)

On Chronograf, I’m using the following:  
chronograf --host “0.0.0.0” --generic-client-id=“okta client id” --generic-client-secret=“okta client secret” --generic-auth-url=“ht(t)ps://myoktadomain.okta.com/oauth2/v1/authorize” --generic-token-url=“[https://myoktadomain.okta.com/oauth2/v1/token”](https://myoktadomain.okta.com/oauth2/v1/token%E2%80%9D)