Add default constructors for CDI beans

Required when proxy beans are created
9 files changed
tree: 035f91bcd973c8d2601abdb05aaf4585275fd491
  1. .github/
  2. .mvn/
  3. scim-client/
  4. scim-coverage/
  5. scim-server/
  6. scim-server-examples/
  7. scim-spec/
  8. scim-tools/
  9. src/
  10. .asf.yaml
  11. .editorconfig
  12. .gitignore
  13. Dockerfile
  15. lombok.config
  16. mvnw
  17. mvnw.cmd
  18. NOTICE
  19. pom.xml


Apache Directory SCIMple

Apache's Java EE implementation of the Simple Cross-domain Identity Management (SCIM) version 2.0 specification as defined by the following RFCs:


Please fork this project and contribute Pull-Requests via this project's Github page. Issue tracking is being transitioned to the Apache Foundation's Jira server.

Please visit our project page at


  • A full-featured Java SCIM client
  • Declarative creation of new ResourceTypes and Extensions
  • Dynamic generation of the Schema and ResourceType end-points.
  • A suite of tools to allow the creation of SCIM resources that can then be verified against the appropriate schemas.

Future features

  • Example implementations of the server with various persistence paradigms.
  • A set of verification tests to ensure the project meets the specification and to allow inter-operability testing.

Example code

Examples of the project's declarative syntax are shown below. The first example shows how a SCIM resource is declared:

@EqualsAndHashCode(callSuper = true)
    id = ScimUser.RESOURCE_NAME,
    name = ScimUser.RESOURCE_NAME,
    schema = ScimUser.SCHEMA_URI,
    description = "Top level ScimUser",
    endpoint = "/Users"
@XmlRootElement(name = ScimUser.RESOURCE_NAME)
public class ScimUser extends ScimResource {

    public static final String RESOURCE_NAME = "User";
    public static final String SCHEMA_URI = "urn:ietf:params:scim:schemas:core:2.0:User";

    description="A Boolean value indicating the User's administrative status.",
    @XmlElement(name = "active")
    Boolean active = true;

    type = Type.COMPLEX,
    description="A physical mailing address for this User, as described in (address Element). Canonical Type Values of work, home, and other. The value attribute is a complex type with the following sub-attributes."
    @XmlElement(name = "addresses")
    List<Address> addresses;

In the example above, annotations are used at the class level and member level to declare a new SCIM resource and its attributes respectively. The example below shows the equivalent declaration for a resource Extension:

    required = false,
    name = "EnterpriseUser",
    id = EnterpriseExtension.URN,
    description = "Attributes commonly used in representing users that belong to, or act on behalf of, a business or enterprise."
public class EnterpriseExtension implements ScimExtension {

    public static final String URN = "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User";

    @Accessors(chain = true)
    public static class Manager {

        description = "The \"id\" of the SCIM resource representing the user's manager.  RECOMMENDED."
        private String value;

        description = "The URI of the SCIM resource representing the User's manager.  RECOMMENDED."
        private String $ref;

This example shows how an extension is declared at the class level, but also provides an example of how complex SCIM types can be simply defined as suitably annotated inner classes.

Implementations are fully customizable without altering the core server code. The example below shows how the implementation for a provider is declared:

public class InMemoryUserService implements Provider<ScimUser> {

Implementing the provider interface allows the customization of create, retrieve, update, and delete methods (as well as find). Customization is flexible - if your system implements soft deletes, create a delete method that simply sets a flag and alter the find and retrieve methods to only return “undeleted” resources.