# OKTA .net core example with authorization flow

**URL:** <https://devforum.okta.com/t/okta-net-core-example-with-authorization-flow/10564>\
**Category:** Questions\
**Created:** [August 18, 2020, 1:11pm UTC](https://devforum.okta.com/t/okta-net-core-example-with-authorization-flow/10564 "2020-08-18T13:11:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![robin.clark1](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@robin.clark1](https://devforum.okta.com/u/robin.clark1)\
**Post date:** [August 18, 2020, 1:11pm UTC](https://devforum.okta.com/t/okta-net-core-example-with-authorization-flow/10564/1 "2020-08-18T13:11:14Z")

</div>

It looks like the okta github examples and walkthrough ([https://developer.okta.com/docs/guides/sign-into-web-app/aspnetcore3/](https://developer.okta.com/docs/guides/sign-into-web-app/aspnetcore3/) ) use a secret id.

My security team is using “authorization flow” which somehow does not use a secret id.

Is there any example of how to configure a .net core web app using this type of authorization?

---

<div class="post-metadata">

**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\
**Post date:** [January 24, 2024, 11:54pm UTC](https://devforum.okta.com/t/okta-net-core-example-with-authorization-flow/10564/2 "2024-01-24T23:54:44Z")

</div>

Closed on January 24, 2024, 11:54pm UTC


