Sign up now for Client Certification Foundation Course - June cohort!
Pure's logos
Pure Help Center for Pure Administrators

If you are a researcher, or other non-admin at your institution, click here.

  • Home
  • Announcements
  • Release Notes
  • Technical user guides
  • Training
  • Events
  • Support
  • Contact Us
  • Home
  • Knowledge base articles
  • Pure Core

How Can We Help?

Search Results

Filter By Category

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact us

Locking Users Out When Doing System ChangesLocking Users Out When Doing System Changes

What

If you want to prevent Users having access to their Pure - maybe because you are upgrading or during maintenance of Pure - and is using a SSO for access, this information below may be useful.

How

If the users are "authenticated by external system", then you can do the following:

  • Create one or two Administrator users that are not authenticated; so do not have the "authenticated by external system" checked in the user setup, if they do not exist already.
  • Once you do this, first test that those users can access your Pure without using SSO. To bypass SSO use "...admin/login.xhtml" at the end of url, this should bring you to the normal Pure login screen.
  • Once you confirm these users can log into Pure without SSO we recommend that you turn off SSO.
    • To turn this off go to Administrator > Security > Admin > Authentication mechanisms, and click "Edit" next to your authentication method and uncheck "Active" and save.
  • When you are ready for your users to access again, then you can go back into Administrator > Security > Admin > Authentication mechanisms and click "Edit" next to your authentication method and check "Active" and save to re-enable SSO.

Again, we strongly recommend that before turning off SSO you test the Administrator users you created to make sure they can access your system without SSO (bypass SSO by adding "...admin/login.xhtml" to the end of your URL).

It would also be a good idea to warn your users that they will be unable to access your system by creating a system message by going to Admin > Messages and text ressources > System messages.

More information

Published at October 24, 2023

Download
Table of Contents
  1. What
  2. How
Related Articles
  • Webservice: How Can I Get Related Content
  • Finding Spaces in XML
  • Bulk Upload ORCID IDs
Keywords
  • 5.13.2-1
  • authentication
  • 5.16.2
  • users
  • single sign on
  • single sign-on
  • lock user account

Was this article helpful?

Yes
No
Give feedback about this article

    About Pure

  • Announcements

    Additional Support

  • Events
  • Client Community
  • Training

    Need Help?

  • Contact Us
  • Submit a Support Case
  • My Cases
  • Linkedin
  • Twitter
  • Facebook
  • Youtube
Elsevier logo Relx logo

Copyright © 2025 Elsevier, except certain content provided by third parties.

  • Terms & Conditions Terms & Conditions
  • Privacy policyPrivacy policy
  • AccesibilityAccesibility
  • Cookie SettingsCookie Settings
  • Log in to Pure Help CenterLog in to Helpjuice Center

Knowledge Base Software powered by Helpjuice

Expand