# Active Directory setup for .Net backed React SPA

**URL:** <https://devforum.okta.com/t/active-directory-setup-for-net-backed-react-spa/3732>\
**Category:** Questions\
**Created:** [December 20, 2018, 8:45pm UTC](https://devforum.okta.com/t/active-directory-setup-for-net-backed-react-spa/3732 "2018-12-20T20:45:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![smartin](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@smartin](https://devforum.okta.com/u/smartin)\
**Post date:** [December 20, 2018, 8:45pm UTC](https://devforum.okta.com/t/active-directory-setup-for-net-backed-react-spa/3732/1 "2018-12-20T20:45:03Z")

</div>

I am tasked with setting up Okta for a project with has a .Net WebAPI backend and the front end being a react (JS) SPA. Currently the application is using a SAML implementation with JWT.

What is the best practise for this scenario? Should I continue to use JWT and drive authentication from the client side? Or is it better to have the client side submit login information to the .Net backend, and perform the authentication from the server side?

Also , does Okta have a AD sandbox? Or do I need to setup my own and connect it to my Okta dev account?

Thanks,  
~Shea M

---

<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 13, 2024, 12:13am UTC](https://devforum.okta.com/t/active-directory-setup-for-net-backed-react-spa/3732/2 "2024-01-13T00:13:29Z")

</div>


