The Hosted Login v2 traditionalAuthenticateMerge Screen: CSS

ImportantIdentity Cloud's 2FA feature is currently in Limited Availability. Please contact your Akamai representative as usage of 2FA features must be approved during Limited Availability.


   

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.


Click here 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>

          </div>

         {* /signInForm *}

    </div>

  </div>

  <div class="additional-actions-container">

    <div class="content-wrapper">

      <span class="help-text"><a href="#" class="aic-control cancel-link" data-action="cancel">{* textSignInCancel *}</a></span>

    </div>

  </div>

  <div class="footer-container">

    <div class="content-wrapper">

        <span class="help-link">{* textNeedHelp *}{* linkHelp *}</span>

        <div class="footer-text">

        {* textFooter *}

        </div>

        <div class="footer-extra-text">

        {* textFooterExtra *}

        </div>

    </div>

</div>

</div>




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). Click a class name for a more graphical look at the class and how it can be styled. Note that the sample shows a generic use of the class and doesn't necessarily show how the class is used on this particular form.


CSS Class

Default CSS

additional-actions-container

.additional-actions-container {
    padding: 25px;
    text-align:center
}

aic-control cancel-link

.aic-control {
   cursor:pointer
}

.cancel-link {
   display: block;
   margin-bottom:10px
}

auth-screen content-wrapper

.auth-screen.content-wrapper {
   max-width:500px
}

capture_signin



content-wrapper

content-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;
   text-align:center
}

footer-extra-text


footer-text


form-action-buttons

.form-action-buttons {
   margin:0 -10px
}

help-link


help-text


screen

.screen {
   min-width:460px
}

screen-description


screen-heading

.screen-heading {
   margin-top:0
}

sign-in-button





Mapping CSS Classes to UI Elements


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





See Also