📄️ How to Integrate the Katanemo SDK in your application (Authorization Runtime Client)?
Katanemo’s Authorization Runtime Client (ARC) is the leight-weight utility that does the intelligent heavy lifting of protecting who can do what on which resource (authorization). As a developer, you can configure ARC at the gateway layer of your SaaS (API) service in minutes. Katanemo offers two primary integration points with varying levels of support to suit your specific environment needs.
📄️ How to Modify the default "tagging match” behavior of Katanemo?
Katanemo’s default behavior is to match tags associated with a resource against tags present in the session token (of the principal) making the request. However, you can alter this default behavior for your particular use case by adding the where clause to your Role policies.
📄️ How to Configure a New OIDC connection?
Each SSO Identity Provider requires specific information to create and configure a new Connection. Often, the information required to create a Connection will differ by Identity Provider. To create an OpenID Connect (OIDC) Connection, you’ll need five pieces of information: a Redirect URI, a Client ID, a Client Secret, a Discovery Endpoint, and a Role.
📄️ How to Configure a New Okta SAML connection?
Each SSO Identity Provider requires specific information to create and configure a new SAML-based Connection. Often, the information required to create a new Connection will slightly differ by Identity Provider. To create an Okta SAML Connection, you’ll need three pieces of information: the Assertion Consumer Service (ACS) URL, a SP Entity ID, and an IdP Metadata URL.
📄️ How to Configure Field-Level Access Control (and filtering) via Katanemo Roles?
Katanemo allows you (a subscriber of a service) to easily construct Roles via OpenAPI semantics (RESTful paths and http methods) that limit operations for a user/machine. This approach requires little to no learning curve in establishing simple yet powerful authorization rules for consuming a service.
📄️ How to use an existing Identity Provider (like Okta, Auth0) with Katanemo?
If you already have an existing login experience and identity provider (like Okta, Auth0) for your service, but want to use the remaining functionality that Katanemo offers (self-service enterprise SSO, fine-grained authorization, safety policies for your API paths and methods, etc.) you can easily use your existing identity pool to work with Katanemo. Your Idp (identity provider) must support JSON Web Tokens (JWTs) for the integration to work effortlessly.
📄️ How to do OAuth2.0 via Katanemo?
📄️ How to invite add users and assign them tags in Katanemo?
To get started, sign-in to the Katanemo Customer Identity & Access Management console, and navigate to the users section of the console