# Okta with custom identity implementation

**URL:** <https://devforum.okta.com/t/okta-with-custom-identity-implementation/4065>\
**Category:** Questions\
**Created:** [January 28, 2019, 7:36pm UTC](https://devforum.okta.com/t/okta-with-custom-identity-implementation/4065 "2019-01-28T19:36:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![molson](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@molson](https://devforum.okta.com/u/molson)\
**Post date:** [January 28, 2019, 7:36pm UTC](https://devforum.okta.com/t/okta-with-custom-identity-implementation/4065/1 "2019-01-28T19:36:12Z")

</div>

I have a site which I’m trying to implement OIDC using the Okta platform as a starting IDP. We may connect to other OIDC providers later but that’s where we’re starting. Anyway, the site exists already and has other authentication methods including [ASP.NET](http://ASP.NET) MVC Identity framework implementation. This has been customized for our particular use cases and so we’re not using the OOB framework classes for Users, Roles, Logins, and Claims. I have run the sample Okta .NET MVC application and it shows my login name after I click the login button. On my site it brings me back to the home page and I do not see my okta username. This leads me to believe it’s not really meshing with the identity implementation on the site.

I guess my question is whether there’s a way to specify which classes and providers need to be used when accepting the OIDC login info?

---

<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 17, 2024, 7:34pm UTC](https://devforum.okta.com/t/okta-with-custom-identity-implementation/4065/2 "2024-01-17T19:34:51Z")

</div>