Code examples not working - OktaDomain not being picked up in settings files

[okta]

Code examples not working - OktaDomain not being picked up in settings files

[laura-rodriguez]

Hi @jabil-rg02,
We apologize for the inconvenience. The Configuration object maps configuration from different providers (i.e Env Vars, JSON files, etc). Maybe your appsettings.json is being overwritten by something else. Can you debug the following code in your Startup class to verify what is mapped to your Okta values?

   .AddOktaMvc(new OktaMvcOptions
            {
                // Replace these values with your Okta configuration
                OktaDomain = Configuration.GetValue<string>("Okta:OktaDomain"),
                ClientId = Configuration.GetValue<string>("Okta:ClientId"),
                ClientSecret = Configuration.GetValue<string>("Okta:ClientSecret"),
            });

https://github.com/okta/samples-aspnetcore/blob/master/okta-hosted-login/okta-aspnetcore-mvc-example/Startup.cs#L43.

Also, as a workaround, you can try to assign those values directly in the Startup class:

In case you don't know, you can test common scenarios quickly with our ASP.NET samples:

• https://github.com/okta/samples-aspnetcore
• https://github.com/okta/samples-aspnet
• https://github.com/okta/samples-aspnet-webforms

I hope this helps.

[jabil-rg02]

I wasn't able to get that example working. I modified the Visual Studio template to work with Okta defaults and provided some screen shots on the readme.md. Feel free to pull the code example and use, I've checked it in to github for our purposes.

Thank You!

[laura-rodriguez]

Hi @jabil-rg02 ,

Have you tried to assign those values directly as I showed you above?

Not sure if the secrets you've posted in the appsettings file in the PR are the ones you are using now, but if so, I highly recommend you to invalidate them. As apparently is the OktaDomain which is failing there's no need to test it with valid client id/secret :).

I've pulled your PR but it has multiple compiling errors. I recommend you to test this using one of our ASP.NET samples instead of the IT projects we have in the ASP.NET solution. Keep it simple, you can remove all the Azure code for now, to narrow down the issue.

I'd be happy to review this again & help you fixing this issue.

[laura-rodriguez]

Also, can you give more background of how is your Login flow?

[jabil-rg02]

I included screenshots in the pull request. The readme file shows all the Okta settings and the code example running