Merge Traditional Account screen (v2) CSS

The traditionalAuthenticateMerge screen is the last step in the merge accounts workflow. This screen appears if:

  1. A user initially created their account by using traditional registration (that is, by supplying an email address and password).

  2. Sometime after creating that account, the user signs in by using a social login provider (e.g., Facebook) that has the same email address used to create their initial account (step 1).

  3. The mergeAccounts screen appears and the user clicks Continue to email.

The traditionalAuthenticateMerge screen then appears and the user is asked to enter his or her Identity Cloud email address and password. After doing so, the user will  be able to sign-in using either their Identity Cloud account or their Twitter account.

Note that you can only merge accounts if the social login provider returns a verified email address as part of its API response.

See Add custom CSS stylesheets for information on overriding the default CSS settings.

Login page HTML

To help you put the CSS classes in context, the following snippet shows the HTML markup used to define the screen, with the CSS classes highlighted using red text. To view the latest HTML for a screen, right-click a blank spot on your Hosted Login login page, click View Page Source, then search for the screen name.

<div style="display:none;" id="traditionalAuthenticateMerge" class="screen">
  <div class="auth-screen content-wrapper">
    <h1 class="screen-heading">{* textMergeAccountAuthScreenHeading *}</h1>
    <p class="screen-description">{* textMergeAccountAuthScreenSubHeading *}</p>
    <div class="capture\_signin">
        {* #signInForm *}
          {* signInEmailAddress *}
{* currentPassword *}
          <div class="form-action-buttons">
            <button type="submit" class="sign-in-button">{* textSignIn *}</button>
         {* /signInForm *}
  <div class="additional-actions-container">
    <div class="content-wrapper">
      <span class="help-text"><a href=""view-source%3Ahttps%3A//\_\_aic\_csrf=fo3YXieocsFVRsd\_&client\_id=64430515-01ea-4f5d-82e4-c36161af0093&code\_challenge=qsPq1vY\_27mtHgxHIiIdBg6LTMGOz1OipZM2Ynn9ETA&code\_challenge\_method=S256&prompt=login&redirect\\_uri&response\_type=code&scope=openid&state=XGW3\_EvXQQ5RqYgGqXYpMMrbFJYpXpPapBX7dvQ0ywo">#" class="aic-control cancel-link" data-action="cancel">{* textSignInCancel *}</a></span>
  <div class="footer-container">
    <div class="content-wrapper">
        <span class="help-link">{* textNeedHelp *}{* linkHelp *}</span>
        <div class="footer-text">
        {* textFooter *}
        <div class="footer-extra-text">
        {* textFooterExtra *}

CSS classes used on this screen

The following table lists all the CSS classes used on this screen; the table also includes the default CSS specified for each class (note that some classes, such as footer-text, are not spelled out in the base.css file).

CSS ClassDefault CSS
additional-actions-container.additional-actions-container {
padding: 25px;
aic-control cancel-link.aic-control {

.cancel-link {
display: block;
auth-screen content-wrapper.auth-screen.content-wrapper {
content-wrappercontent-wrapper {
background-color: #fff;
box-shadow:1px 1px 5px 2px rgba(0, 0, 0, .1)
footer-container.footer-container {
padding: 25px;
border-top: 1px solid #f2f2f2;
form-action-buttons.form-action-buttons {
margin:0 -10px
screen.screen {
screen-heading.screen-heading {

CSS classes mapped to UI elements

The following graphic maps CSS classes to the more-visible UI elements used in the screen:

See also