Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

Purpose

The purpose of this module is to demonstrate customization of the user interface and support for localization.

Requirements

This lab requires you have access to SSO and CustomerID administrative interfaces.



Overview

Ubisecure Identity Server is designed with customization in mind. The customer decides the branding and customization requirements, and usually a system integrator is in charge of the customization and localization project. The main components that can be customized are:
  • Colors and Logos
  • Internationalization and localization
  • Terms and Conditions
The expected outcome of this lab is multi-language support with customized logos and colors.

SSO Customization

  • In practice, customizing Ubisecure SSO is reflected in the login screens of the customer application
  • UI Customization is mainly based on the web agent (application)
  • Language selections can be made by the user if multiple languages are enabled for the application in question
  • Both the visual and internationalization customization can be based on the web agent requesting the authentication

Page layout

The following image shows all the elements that can be customized in a SSO/CustomerID page:


Example login screen

The following image is an example of a real user interface created by a Finnish customer, DNA. Observe and compare it with the previous image.



Homework

For more information about the Template API, see Template API

Some files you will need for these exercises

Before you start, please download these files to your instance:

Example configurations.zipfavicon.icosmartplan.svg

Unzip Example configurations.zip file to your Desktop


Customization and localization in practice

Now we'll have several exercises in which you will customize the user interface of the installation on your own computers.



Part 1: Colours and Logos – Login Screens

See page SSO Login UI Customization on Developer and Partner Portal.
The goal of this exercise is to create a custom template with own SmartPlan logo and colors.

Ubisecure's default login pages use blue color with ASCII code #0c73ac

Step 1: Adding a new template

1. Add new template reference to

C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\template.index

c:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\template.index
smartplan = templates/smartplan.properties

2. Create new UI Template
In C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\templates\ copy the file default.properties to smartplan.properties.
Add the following line to smartplan.properties

c:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\templates\smartplan.properties
logo.svg = /resource/smartplan.svg


3. Copy smartplan.svg to c:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\resources\


copy C:\Users\Administrator\Desktop\Ubisecure\smartplan.svg "c:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\resources\"
 
4. Add the following line to C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\resource.index
custom/resource.index
smartplan.svg = resources/smartplan.svg

Step 2. Configuring templates to applications

1. Now add the new template to Smartplan application. This will assign all your modifications (saved as template "smartplan") to the SmartPlan application, which controls the login user interface. On SSO Management console, open: SmartPlan, Applications and SmartPlan Application. Write smartplan in the field "UI Template Names." Click "Update."

2. Also, add the template to the CustomerID Adminstration interface.

The CustomerID Administration application is located in the "eIDM Services" site, under Applications. It is called eidm2.

Before:

After:

Press Update.

3. Finally, restart UbiloginServer service. The changes can take a few minutes to take effect.

In the future, you can follow the same steps to add a template for any application.

Step 3. Verify the login screen changes

Go to SmartPlan application to verify the changes in the login screen:

http://localhost:8090/smartplanapplication/

Part 2: Colors and Logos – CustomerID User Interface

You will change default colors in CustomerID user interface by editing and making your desired changes on the CSS file C:\Program Files\Ubisecure\customerid\application\custom\style.css

Step 1: Change colors

1. Copy C:\Program Files\Ubisecure\customerid\tools\examples\custom\style.css to C:\Program Files\Ubisecure\customerid\application\custom\style.css
2. Open style.css with a file editor. Search for #0c73ac (default Ubisecure's blue) and replace all its occurrences with #FF6600 (SmartPlan's orange).

3. Go to Customer ID user interface.

https://login.smartplan.com:7443/eidm2/wf/admin

The user interface will change from blue to orange elements:


Step 2: Modify favicon

Modify CustomerID's favicon

Copy the new favicon.ico file from C:\Users\Administrator\Desktop\Ubisecure\ into C:\Program Files\Ubisecure\customerid\application\custom\


In order to modify CustomerID's default logo, you must use a PNG/JPG file. SVG is not a valid format.

Copy and rename the logo file from C:\Users\Administrator\Desktop\Example configurations\SSO\custom\smartplan.png to C:\Program Files\Ubisecure\customerid\application\custom\logo.png


Step 4: Verify the changes in the Customer ID user interface.

1. Restart the Wildfly service.

2. Reload the Customer ID user interface window. Note! You might have to clear the browser cache and restart the browser before modifications take effect.



Part 3: Internationalization and localization 

Login Screen

Login screen has the following customization options:

Step 1: Messages

You can customize the texts shown to users during the login phase as they are customizable message files. The message.index file holds an index of UI message files. Ubisecure SSO comes pre-configured with default (English) texts for all supplied authentication methods. To override the default uas, or errors messages, add an entry named uas, or errors to message.index.


  1. Add new references to C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\message.index as seen in the box:
    custom\message.index
    uas = messages/uas.properties
    errors = messages/errors.properties
    uas_fi = messages/uas_fi.properties
    errors_fi = messages/errors_fi.properties
    uas_sv = messages/uas_sv.properties
    errors_sv = messages/errors_sv.properties
    
    
  2. Make directory C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\messages\
  3. Create a new properties file errors.properties in C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\messages folder
  4. Add a string in the user interface to make the error message a bit more friendly.
      

    errors.properties
    USER_NOT_FOUND = Hey :) We didn't find you. Would you try again?

    Now try to log in with a nonexistent user name, and observe the message that appears in red letters.

  5. Add new languages to templates for selection. You must edit C:\Program Files\Ubisecure\ubilogin-sso\ubilogin\custom\templates\smartplan.properties file.  (For reference, full values of default.properties file are in Template files page)

    default.properties
    defaultlocale = fi
    locales = en, fi, sv
    localenames = in English, Suomeksi, på svenska
    
    
    

    Go to the login screen of the My Smart Plan application to see the changes. 

    Note, if the Nordic letters don't display properly, change the enconding of the smartplan.properties file to ANSI in the text editor.

  6. Optional exercise: Add a new language to a template

    Repeat the step 5 to add a new language.

Step 2: Workflows

User interface localization
  1. Change the default language to Finnish. In order to do this, edit C:\Program Files\Ubisecure\customerid\application\custom\eidm2.properties

    custom\eidm2.properties
    default.locale = fi
  2. Change the default texts in "Front Page" that appears in CustomerID Administrative Interface. The steps are:

    1. Create file C:\Program Files\Ubisecure\customerid\application\custom\messages_fi.properties  

    2. Copy the file C:\Program Files\Ubisecure\customerid\tools\examples\custom\messages_fi.properties to C:\Program Files\Ubisecure\customerid\application\custom\messages_fi.properties

    3. Then edit the key: admin.frontpage.welcometext1 = Smartplan järjestelmän organisaatiot.

    4. Restart the Wildfly service.
    5. Go to the CustomerID front page to verify the change.

Step 3: Role and attributes

  1. Localized role descriptions. Edit C:\Program Files\Ubisecure\customerid\application\custom\roles.properties

  2. First observe the contents of the file. Then localize SmartPlan role descriptions by editing the custom roles.properties configuration.

    roles.properties
    fi.friendlyName.mainuser = Yhteyshenkilö
    fi.friendlyName.user = Edustaja
    
  3. Localized attribute descriptions. By editing the custom messages_fi.properties file add the line:
       

    messages_fi.properties
    organization.crmid = CRM ID
    

    Restart the Wildfly service.

Step 4: Terms and Conditions


You can also edit the "terms and conditions" in several languages.
  1. Create the file terms_fi.html (Terms and Conditions in Finnish) to C:\Program Files\Ubisecure\customerid\application\custom  (This will be used in later exercise).


    terms_fi.html
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
    <html>
        <body>
            SmartPlan terms in Finnish
        </body>
    </html> 



Part 4: Discovery and Template APIs

Step 1: Discovery UI API

Enable third-party implementations of

  • authentication method selection user interfaces
  • dynamic handling of identity provider selection

Example

  • Mobile application selection
  • Java-script method selection implementation in SP application

Example:




Step 2: Template API

Template API allows for a consistent and safe reference method to elements required for providing custom user experiences

Examples

  • Dynamically showing currently supported authentication methods within an third-party application

Benefits

  • Reducing redirections
  • Faster user experience
  • Consistent API across future product releases

Examples:

To get the page logo in Finnish for the template named default:

To get the logo in Finnish for the authenticaiton method called sms.otp.1:

  • No labels