This documentation is in progress and includes all updates released after Identity Server 5.4.1. For documentation specific to a version, see About This Release.
Page Comparison - Editing Claim Dialects (v.1 vs v.2) - WSO2 Identity Server 5.x.x - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can edit existing claim dialects by clicking on any available dialect link. Follow the instructions below to edit a claim dialect.:

  1. Sign in. Enter your username and password to log on to the Management Console.
  2. Click Main to access the Main menu and click List under Claims.
  3. Click on any available dialect links.
  4. From the Claim Dialect view, you can view the claims defined for that particular dialect. If you need to edit a claim, click on the appropriate Edit link.
  5. Enter the new claim information in the required fields and click on the Update button.

    AttributeDescriptionSample value
    Display NameThe name of the claim value which is display to the user.
    Street Address
    DesciptionA small description of the claim to help the user to understand it easily.
    Address of the street
    Claim UriThe URI which defines the claim.
    Mapped AttributeThe attribute which mapped to the claim.
    Regular Expression
    Regex which
    A regular expression that helps to verify the input.
    A street address can be an integer or a string, therefore regex can be like "^\d{1,45}$ "
    Display OrderOrder to display claims.
    Supported by DefaultWhether the claim is displayed in the profile of the user.Enabled
    or disabled
    RequiredWhether the claim is mandatory.Enabled
    or disabled
    Read-onlyWhether the claim cannot be updated later
    (Read only).Enabled
    or disabled

    When you are using more than one user store, you must map the attributes correctly using claim management. Under “Mapped Attribute(s)” you need to follow the pattern.

    Code Block
    {domain_name/attribute_Name};{domain_name/attribute_Name}; {domain_name/attribute_Name};

    However, for the default user store, you do not need to provide the domain name. As an example, if you have two user stores, one is the default and another one with domain “LDAP” then the pattern would be as follows for “".

    Code Block