Summary
SCIM request logging is an option in the Integrations SCIM provisioning settings that records provisioning activity between your identity provider and KnowledgeCity. When it is enabled, you gain a record of the requests and responses exchanged during provisioning, which you can review to confirm that accounts are being created and updated as expected and to troubleshoot problems.
Introduction
SCIM request logging is part of the SCIM User Provisioning configuration inside the KnowledgeCity Integrations settings. SCIM (System for Cross-domain Identity Management) lets your identity provider synchronize users into KnowledgeCity automatically, and the logging option captures the provisioning activity that flows through that connection so it can be reviewed later.
This feature is intended for administrators who manage SCIM provisioning at scale. It solves the problem of provisioning being a silent background process: without a record, it is hard to tell whether users are syncing correctly or why a particular account did not appear. Enabling logging gives you that record so you can verify behavior and investigate issues.
Key Concepts
- SCIM request logging: the option that records provisioning activity, including the requests and responses exchanged, so you have a reviewable history of what your identity provider sent and how KnowledgeCity responded.
- SCIM provisioning: the automatic creation and updating of KnowledgeCity user accounts driven by your identity provider through the SCIM protocol.
- Identity provider: the external directory or system that sends user data to KnowledgeCity through SCIM and that generates the activity you can log.
- Provisioning event: a single create or update action that SCIM performs on a user account, and the unit of activity that logging captures.
- Troubleshooting record: the logged activity you consult to confirm successful provisioning or to trace why a specific account was not created or updated as expected.
Steps to Follow
Open the Integrations settings
Sign in to KnowledgeCity as an administrator. From the Settings menu, select Integrations to open the configuration area where SCIM user provisioning is managed.
Confirm SCIM provisioning is enabled
Locate the SCIM provisioning option and make sure it is turned on. Logging records the activity produced by provisioning, so the connection between your identity provider and KnowledgeCity needs to be active for there to be anything to log.
Enable the logging option
Within the SCIM provisioning settings, set the logging option to on. Once enabled, provisioning activity is recorded as your identity provider sends requests, giving you a history of how users are being created and updated.
Generate provisioning activity
Trigger provisioning from your identity provider, for example by adding or updating a user that is in scope for KnowledgeCity. Each provisioning event your identity provider sends produces activity that the logging option captures while it is enabled.
Review the logged activity
Use the recorded logging to confirm that accounts are being provisioned correctly. Check whether the expected create and update events appear and whether each one succeeded, so you can verify that your identity provider and KnowledgeCity are in sync.
Troubleshoot with the logs
When a user does not appear or an update does not take effect, review the logged requests and responses for that provisioning activity. The record helps you see what your identity provider sent and how KnowledgeCity responded, so you can pinpoint where the provisioning broke down and correct the configuration.
Conclusion
SCIM request logging turns provisioning from a silent process into a reviewable one. By keeping SCIM provisioning active and enabling the logging option, you gain a record of the requests and responses that flow between your identity provider and KnowledgeCity, giving you a reliable way to confirm that users are syncing correctly and to troubleshoot provisioning issues when they arise.