@import url('/cas/css/cas-a90aca7e2afb259734284377211db332.css?disableCache7');

button.mdc-ripple-upgraded--background-focused {
}

label.mdc-text-field {

}

.cas-logo {
    display:none
}

#app-bar nav {
    height: 84px;
}

.mdc-top-app-bar--fixed-adjust {
    padding-top: 84px;
}

#app-bar nav section:first-child {
    background: url(/cas/images/logo-38790c640230391cffa002d1ff88d798.png) no-repeat;
    width: 350px;
    height: 65px;
    background-size: contain;
    margin-top: 9px;
    margin-left: 15px;
}

:root {
    --cas-theme-primary: #5179B4;
    --cas-theme-secondary: #969590;
    --mdc-theme-body: rgb(245, 245, 245);
    --mdc-switch-selected-track-color: #e0e0e0;
    --mdc-switch-unselected-track-color: #e0e0e0;
    --mdc-switch-unselected-focus-track-color: #e0e0e0;
    --mdc-switch-selected-focus-track-color: #e0e0e0;
    --cas-theme-danger: #b00020;
}

/*
 * CAS 7.3 hardcodes a photo background on the content wrapper in its own header fragment
 * (cas-server-support-thymeleaf, templates/fragments/header.html) - it is not gated on a theme key,
 * so it cannot be switched off from cas.properties or the theme file. Overriding the class here is
 * cheaper than shadowing that whole fragment, which would have to be kept in sync on every upgrade.
 * The rule lives in an inline <style> the browser sees after this stylesheet, hence !important.
 * With the image gone, the page shows the body background again - our --mdc-theme-body above.
 */
.bgimage {
    background-image: none !important;
}

#serviceui {
    background-color: rgb(245, 245, 245);
    margin-top: 10px;
}


#serviceui div img {
  max-width: 150px;
}

#servicedesc {
    line-height: 5px;
    padding-left: 25px;
    padding-top: 20px;
}

#servicedesc h5 i {
    display: none;
}

#selectIdentityProvider {
    display: none;
}

#strengthProgressBar .mdc-linear-progress__primary-bar {
    display: contents;
}