# Connect identity

Bring people, AI agents and their role membership in from your identity manager, which stays the master of who exists, while the roles themselves are created in Straza.


- [midPoint](https://docs.straza.ai/guides/connect-identity/midpoint/index.md) connects midPoint over SCIM, so users, agents and role membership arrive from your IGA and leave when it says so.
- [Okta](https://docs.straza.ai/guides/connect-identity/okta/index.md) provisions people and their role membership from Okta over SCIM.
- [Keycloak login](https://docs.straza.ai/guides/connect-identity/keycloak-login/index.md) makes Keycloak the login provider, so people sign in with their own identity and Straza never holds a password.
- [Entra ID login](https://docs.straza.ai/guides/connect-identity/entra-login/index.md) makes Microsoft Entra ID the login provider, with the app registration and the claim the browser sign-in needs.
- [Okta login](https://docs.straza.ai/guides/connect-identity/okta-login/index.md) makes Okta the login provider, with a native app and the fixed port its redirect needs.
- [Generic SCIM](https://docs.straza.ai/guides/connect-identity/generic-scim/index.md) connects any SCIM 2.0 client with the profile the server accepts.
- [AI agents as identities](https://docs.straza.ai/guides/connect-identity/nhi-provisioning/index.md) provisions an AI agent from your identity manager, registers the key it signs in with, and retires it again.


- [midPoint](https://docs.straza.ai/guides/connect-identity/midpoint/index.md): midPoint provisions people and AI agents into Straza over SCIM, hands them Straza roles through access packages, and takes both away again.
- [Okta](https://docs.straza.ai/guides/connect-identity/okta/index.md): Okta provisions people and their Straza role membership over SCIM, and you know what each request Okta sends does in Straza.
- [Keycloak login](https://docs.straza.ai/guides/connect-identity/keycloak-login/index.md): strazad trusts your Keycloak realm, people sign in to Straza with their own Keycloak identity, and Straza never holds a password.
- [Entra ID login](https://docs.straza.ai/guides/connect-identity/entra-login/index.md): People sign in to Straza with their Microsoft Entra ID account, in a browser on the machine they enroll, and strazad trusts your tenant's ID tokens.
- [Okta login](https://docs.straza.ai/guides/connect-identity/okta-login/index.md): People sign in to Straza with their Okta account, in a browser on the machine they enroll, and strazad trusts your Okta authorization server's ID tokens.
- [Generic SCIM](https://docs.straza.ai/guides/connect-identity/generic-scim/index.md): Your SCIM 2.0 client holds a token for Straza, and you know each request Straza accepts, what it does and how Straza refuses the rest.
- [AI agents as identities](https://docs.straza.ai/guides/connect-identity/nhi-provisioning/index.md): An AI agent provisioned by your identity manager signs in to Straza with its own key and no browser, and leaves again when the identity manager retires it.
