Maintaining Logins and Passwords

This section covers the following topics:

Changing the super admin credentials

Follow the instructions below to change the default admin password:

  1. Go to <API-M_HOME>/repository/conf/deployment.toml and change the user credentials as below.
    username = "your-name"
    password = "your-password"


Do you have any special characters in username or passwords?

  • Above credentials are applied to relevant xml configuration files such as user-mgt.xml.

    If you specify passwords inside XML files, you have to be mindful when giving special characters in the user names and passwords. According to XML specification ( ), some special characters can disrupt the configuration. For example, the ampersand character (&) must not appear in the literal form in XML files. It can cause a Java Null Pointer exception. You must wrap it with CDATA as shown below or remove the character:

  • Above credentials are applied to file.

    • It is not possible to use the @ symbol in the username or password.
    • It is also not possible to use the percentage (%) sign in the password. When building the connection URL, the URL with credentials is parsed. This parsing exception happens because the percentage (%) sign acts as the escape character in URL parsing. If the percentage (%) sign in the connection string is required, use the respective encoding character for the percentage (%) sign in the connection string. For example, if you need to pass adm%in as the password, then the % symbol should be encoded with its respective URL encoding character. Therefore, you have to send it as adm%25in. For a list of possible URL parsing patterns, see URL encoding reference. Add the following configuration.

Therefore, if you have special characters, add the following configurations. If you have special characters, be mindful to wrap values with CDATA tag in super_admin configurations and to encode values in apim.throttling.jms configurations.

   username = "your-name"
   password = "<![CDATA[your-password]]>" 

   username = "your-name"
   password = "your-encoded-password"        


Note that the above password is written to the primary user store when the server starts for the first time. Thereafter, the password will be validated from the primary user store and not from the configuration file. Therefore, if you need to change the admin password stored in the user store, you cannot simply change the credentials as above. To change the super admin password, you must use the Change Password option from the management console.

To change the password from Management Console ( https://localhost:9443/carbon ), follow the steps in Changing a Password corresponding to API Manager.

Recovering a password

Use the <API-M_HOME>/bin/ script.


If you encountered an error similar to ant: command not found, Please install ant before running the above script

Setting up an e-mail login

For information, see Email Authentication in the WSO2 IS documentation.

  • When setting up email login, specify the complete username with tenant domain. If you are in the super tenant mode the username should be as follows. <email>@carbon.super

    Example: [email protected]@carbon.super

  • The "@" character is a reserved character in the WSO2 messaging component. Therefore, when specifying the username in JMS Connection URL, under apim.throttling.jms.username section in the <PRODUCT_HOME>/repository/conf/deployment.toml file, "@" characters should be replaced by "!" character. An example is shown below.


Setting up a social media login

You can auto-provision users based on a social network login by integrating the API Manager with WSO2 Identity Server. Refer Log in to the API Developer Portal using Social Media for more information.


Note that auto-provision users based on a social network login are not supported in a multi-tenant environment.


In a multi-tenant environment, the system cannot identify the tenant domain in the login request that comes to the API Manager's Publisher/Developer portal. Therefore, the service provider is registered as a SaaS application within the super tenant's space. Configuring user provisioning is part of creating the service provider. In order to authenticate the user through a third-party identity provider such as social network login, you must enable identity federation. As the service provider is created in the super tenant's space, the provisioned user is also created within the super tenant's space. As a result, it is not possible to provision the user in the tenant's space.

To overcome this limitation, you can write a custom authenticator to retrieve the tenant domain of the user and write a custom login page where the user can enter the tenant domain, which is then added to the authenticator context. Then, write a custom provisioning handler to provision the user in the tenant domain that is maintained in the context.