Setting up a user and user token for SCIM provisioningDon't forget to come by and check out our new RESTful JSON APIs, they can help you utilize and extend Quickbase with ease.
To provision users via the SCIM API endpoints, you need to use a Quickbase user with realm admin and account admin privileges. The user can either be an existing, individual user, or a shared system user. See below for guidance on setting up a system user.
The user for provisioning also requires a user token. For steps on creating a user token, read About User Tokens. Once the user token is created, you include the user token in an
Authorization header with a type of
Setting up a system user
You can use a shared system user to help ensure that provisioning occurs without interruption.
Note: A system user isn’t included counted as a paid Quickbase user unless the user is also used to share apps, like a normal Quickbase user.
If you are not using SAML authentication for your realm, create a system user in Quickbase with realm admin and account admin privileges. Contact Quickbase Customer Care if you need help assigning realm admin privileges to this user.
If you are using SAML authentication for your realm, system user creation varies depending on how your realm is configured:
If your realm is set to require SAML authentication for all users, create a system user in your SAML directory, and then use your normal process to add the user to Quickbase with realm admin and account admin privileges.
If your realm is not set to require SAML for all users, you can either use the SAML process or create the user directly in Quickbase.
Is this help page useful? Rate it:
© 1999-2021 Quickbase, Inc. All rights reserved. Legal Notices.