Skip to main content
Use the @bijection/connectors/sap-concur entrypoint to declare SAP Concur resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Identity v4.1 users

observed: SCIM search by meta.lastModified with a carried basis

The following example matches configuration standard.

Configuration: standard

Case: sap-concur/users/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: sap_concur. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

sapConcur.users.observed({ lag? }) reads the company’s users through Identity v4.1 (SCIM 2.0) under the binding’s baseUrl, the company’s geolocation such as https://us2.api.concursolutions.com/. Each pass posts profile/identity/v4.1/Users/.search with meta.lastModified ge "…" and continues with the stated nextCursor, sent back in the same search body. The first page’s Date is the pass’s basis and the next pass begins lag seconds (default 300) before it. Concur documents no sort for the search and does not say whether a cursor can step over a user that still matches while the pass pages; this recipe assumes it cannot. Published: id, userName, displayName, active and lastModified (the version). A deactivated user is published with active: false; the rare hard delete is not observed. No command is declared. Expense reports are not read: the v4 Expense API is per user, and the company-wide v3 listing pages by offset. Bind a sap_concur credential: an oauth_refresh grant of a company-level token (/oauth2/v0/token). No Concur company has been reached.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.