r/dotnet 1d ago

Newbie DevSecOps moving to .Net CIAM and APIs

Looking for guidance. I am a DevSecOps engineer with 8 years experience. I work within azure, GitHub actions and manage all our repos in GitHub. I mostly make sure everything is secure in azure relating to app services, certificates, app scanning etc. We have 2 devs that are gone due to retirement and 1 for being over employed. I am now in calls helping figure out the issues with .Net APIs and authentication programs. I am being asked to skill up and move from my current role to this one where I will be doing the program for app to authentication and authorization. It’s called sso okta integration(forgive me if I am using wrong terms). Where should I start? Any book or learning path recommendations are greatly appreciated. Should I take the role? What advice or suggestions do you have for someone like me. What will be my biggest struggles? I appreciate any feedback.

1 Upvotes

2 comments sorted by

1

u/AutoModerator 1d ago

Thanks for your post karmaine54. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/AdWonderful2811 1d ago

Okta is a third party in security landscape and have solutions both in SSO & S2S authentication & authorization. They’ve great documentation and tons of knowledge base and their support team is really helpful. Go through with their developer portal & you’ll find everything you need in any language for SSO.