New Admins: Register for our new Pure Lecture Series!
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
  • Training
  • Technical user guides
  • External authentication mechanisms

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

Basic authenticationBasic authentication

Can only be used in WS scope after 5.30.0

It is automatically enabled on WS scope and is automatically used if parts of WS requires authentication.

No longer supported to be used as authentication for admin

 

 

With this mechanism Pure can authenticate by procesing the HTTP request's BASIC authorization headers. Processing is done on any request that has a HTTP request header of Authorization with an authentication scheme of Basic and a Base64-encoded username:password token. For example, to authenticate user "Aladdin" with password "open sesame" the  following header would be presented: Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==

Required configuration steps

No configuration required

Optional configuration

  • The Realm name can be configured. This will be presented to the user. 

Published at June 27, 2024

Download
Table of Contents
  1. Can only be used in WS scope after 5.30.0
Related Articles
  • Request remote user based authentication (Pre 5.30.0)
  • Static user authentication (Pre 5.30.0)
  • Request header based authentication (Pre 5.30.0)
  • External authentication mechanisms
Keywords
  • basics
  • authentication

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