SCIM Connector Project Configuration

The project's resource folder contains all build time configurations for the SCIM connector.

• application-connector.yml - Project and Connector specific configuration.
• application.yml - Core Connect SDK configuration. These are mostly default configurations and core settings.
• bootstrap.yml - Server/Container configuration. This file includes settings for all different environments and follows the spring profile standards.
• logback-spring.xml - Log configuration also supports different configurations based on spring profiles.

It is possible to have dedicated configuration files for each environment. This is often used to override a common setting for a particular environment. To create such a file, follow SpringBoot's format having the additional desired spring profile name at the end of the application.yml file, for example, application-dev.yml

`aws-secrets-manager`

1fluent-connect:
2  connector-name: "scim-connector"
3
4  fluent-account: "CNCTSSO"
5
6  cache:
7    caffeine:
8      - name: location
9        expiry-in-seconds: 300
10        max-size: 10000
11      - name: retailer
12        expiry-in-seconds: 300
13        max-size: 10000
14
15  user-update:
16#    enable when a scim-connector client implements role handling according to SCIM RFC-7644 Spec (with add,replace,remove roles patch ops)
17    renderFluentRoles: false
18
19  enable-listeners: false
20
21  credential:
22    credential-manager: "aws-secrets-manager"
23
24  security:
25    web:
26      publicEndpoints:
27        - "/actuator/**"
28        - "/api/docs"
29        - "/swagger-ui.html"
30      customAuthFilters:
31        - "com.fluentcommerce.connect.core.web.security.filters.ScimApiKeyAuthenticationFilter"
32

Cache

Configuration for the cache is mentioned here

By default, the SCIM Connector requires two cache keys:

• `Location`

  : This cache stores the details of the location obtained by using the CONTEXT_ID when the CONTEXT_TYPE is set to AGENT.

• `Retailer`

  : This cache stores the retailer's details obtained using the CONTEXT_ID when the CONTEXT_TYPE is set to RETAILER.

Security

Configuration for security is mentioned here.

Proper security configuration for the Authentication Filter is essential to establish a secure connection between SCIM and its client.

1  security:
2    web:
3      publicEndpoints:
4        - "/actuator/**"
5        - "/api/docs"
6        - "/swagger-ui.html"
7      customAuthFilters:
8        - "com.fluentcommerce.connect.core.web.security.filters.ScimApiKeyAuthenticationFilter"

`publicEndpoints`

• Authentication credentials should not be required for any requests made to those endpoints.
• Requests that do not correspond to any of those endpoints should be prohibited.

Although these endpoints are designated as public, all requests made through them will still pass through the Authentication Filter Chain. This means that even if custom authentication filters are specified, and an attempt is made to add authentication to the header, the filter will still verify it.

`customAuthFilters`

• To ensure proper security, the SCIM connector will use the security module provided by the Connect SDK: 

  `connect-sdk-web-security`

  , with a custom Authentication Filter, added. The authorization request header sent to Fluent must adhere to Fluent's security specifications.
• The default Authentication Filter used is 

  `ScimApiKeyAuthenticationFilter`

  .