Add a custom internal application that is not using SAML or SWA in order to leverage API
I am working on putting a custom Java application behind Okta for authentication purposes. In order to properly leverage the Authentication API, it seems that I need to add this application to Okta via the admin application and then assign permissions to the specific AD groups.
When I attempt to add an application in Okta's admin application, the only options are for a SAML or SWA application. Because this application is only used internally, it is not currently utilizing SAML or SWA.
Once this custom application is added to my company's Okta, I can assign certain AD group permissions and make my Authentication API calls by passing in the current AD username and AD password. The API will then check the user's group permissions, either granting or denying access. (Does this sound correct?)
Is there a way to add a custom-made application in Okta's admin application without SAML or SWA, in order to utilize the AD group permissions in tandem with the Authentication API?
Thanks for posting your inquiry in Okta Community.
You can use the other methods of integrating other non-SWA, non-SAML applications by configuring "Okta Template App and Template Plugin App". Please refer to the link below for more detailed informaiton.