How do I upload a template?¶
Preparing git repository¶
When preparing the git repository, please use the proper directory structure.
├── cim ├── extension-resources ├── email-templates ├── messages ├── static | ├── css | ├── images | └── js └── templates └── personal ├── access ├── <template-set-name> ├── ├── default ├── ├── messages ├── delegation ├── locales ├── <locale code> ├── translation.json ├── logo.png ├── palette.json ├── favicon.ico
cim directory contains templates and messages for login and sign up. Within the
extension-resources folder, you can add any of the following folders:
- Email templates: templates for emails.
- Messages: key-value messages in multiple languages.
- Static: js and CSS, images, and other static resources.
- Templates: templates displayed in the frontend.
access directory contains template sets used to change your web applications and mobile clients' look and feel. Refer to the Access component documentation to learn more about switching the template set per client and the contents of a particular template set. The name of the directory is resolved as the name of the specific template set. If the template cannot be found in the chosen set's directory, the content will be served from the
messages subdirectory contains message bundles that the Access Engine application will load. Please note that there is one folder for
messages that are used by all template sets.
delegation directory contains resources that allow customizing the web experience in Delegated Administration for Business Partners (DABP). You can customize the following resources:
- Translations: key-value messages in multiple languages. Please refer to the example
- Logo: use
- Favicon: use
- Application theme: use
palette.jsonfile, more information available here
Create git repository connection¶
- Log into Onegini Customer Identity Access Manager >
- The window Frontend styling opens:
Fill in the following fields:
Field Description Remote location The remote location to clone the Git Repository. It must start with
sshis not supported.
No authentication required Enable this option when your GIT repository is publicly accessible. This option is disabled by default which means that the Git Repository is private and protected by a username and password. Username The username for the git repository. Password The password for the git repository. Instead of using a password, you can generate a GitHub personal access token here: Personal access tokens.
Click [Next: select reference]. (The form has been validated and stored.)
After completing the steps under Create Git repository connection, the Select a Reference-window opens:
In the 'Select a branch' or 'Select a tag' field, all the available remote tags (when working in a staging or production environment) and branches (when working in a development or testing environment) can be selected. The first tag or branch in the list will be preselected.
- When the correct tag or branch is selected, click [Save]. The branch or tag is stored, and synchronization will happen automatically.
- After saving, the overview page is displayed:
The overview page shows the following information:
|Clone URL||The remote URL of the GIT repository.|
|Authentication||The authentication method to access the GIT repository, for example, 'basic'.|
|Username||The username, only required if the authentication method is "Username and password".|
|Branch or Tag||The selected branch or tag for the templates and translations.|
|Last checked||The last time the resources have been fetched from the remote repository.|
To edit the Git repository connection, click [Edit connection].
To change the reference, click [Change reference].
To synchronize a Git Repository, click [Synchronize] in the overview page:
- During synchronization, the external resources (HTML/CSS/images) are fetched from the selected Git repository and stored on the server.
- After synchronization, the templates are uploaded to your environment. You can now start testing the templates, for example, by loading the login page.
Changes in the templates will only be visible on the production environment after clearing the CIM cache (or restarting the application). Please ask your contact within Onegini.