My company is a division of a much larger company that uses Okta extensively. My team is getting ready to do a rewrite of an old system. Our front-end clients will be native Windows 10 applications. Ideally, clients will authenticate with Okta to be able to access our web services. These WILL NOT be web-based clients. The client machines will be locked-down. Users will not be able to use any application except ours -- not even a browser.
Is it possible to leverage Okta under these circumstances? If so, what is the best way?
I know this comes as a late answer, but it took me some time to go through some hoops to get this code sample published. In your scenario, you'd rather look at our OpenID Connect feature combined with our API Access Management (http://developer.okta.com/use_cases/api_security/" target="_blank) product, which is Okta' implementation or OAuth 2.0.
The code sample I previously discussed is available on GitHub (https://github.com/oktadeveloper/okta-oauth-nativewindows" target="_blank) and is an example of a console-based app leveraging the default OS browser (and potentially an existing Okta session if the user is already logged in) to authenticate the user and let him acquire an ID Token as well as, optionally, an Access Token that can be used against a web service ("resource server" in OAuth lingo) that leverages that access token for authentication and authorization purposes.
The Resource Server/Web Service code sample is not fully ready yet (it still has to be fully code reviewed and approved by legal) but I hope to have it available soon. You can start playing around with the console app above though. I look forward to your feedback!