Adding App ID overview
You can quickly add authentication and authorization to your application by integrating App ID. Regardless of the type of flow that you use, you can securely authenticate users to your app. With authentication in place, you can provide personalized user experiences across all types of devices.
Check out the following table to see how App ID fits into each type of application.
| Type of authentication flow | Description |
|---|---|
| Single-page | You can use the single-page flow to securely authenticate users to your applications. An SPA runs entirely in your browser and does not require that the page be reloaded while the application is in use. |
| Web | You can use the web flow to securely authenticate users to your application and protect your server-side resources. If your application has a backend that you manage, it's recommended that you use the web flow. |
| Mobile | The App ID mobile flow is most helpful when you're developing applications that are made to be installed on a user's device as a native application. |
| Backend | You can protect your development resources and API endpoints from unauthorized access and ensure the security of your app by using the backend flow. |
| Custom | Already have your own custom flow? No problem. You can use the custom identity flow to integrate App ID with your app. |
| Anonymous | With App ID, you can begin tracking a users activity before their initial sign-in to your app by using anonymous authentication. |
| Ingress | With App ID, you can consistently enforce policy-driven security by using the Ingress networking capability in IBM Cloud Kubernetes Service. |
| Istio | By using the App Identity and Access adapter, you can centralize all your identity management in a single place. Because enterprises use clouds from multiple providers or a combination of on and off-premise solutions, heterogeneous deployment models can help you to preserve existing infrastructure and avoid vendor lock-in. |