November 2, 2020
When applying PostgreSQL security features to the AAA framework—which stands for Authentication, Authorization, and Auditing—step one is Authentication. This means verifying that the user is who he or she claims to be.
The PostgreSQL host-based access file restricts access based on user name, database, and source IP—if the user is connecting via TCP/IP. Authentication methods are assigned in this file as well. The authentication method or methods you choose depend on your use case.
Methods include Kerberos/GSSAPI, SSPI, LDAP and RADIUS, Cert, md5, Scram, Reject, and Trust. It’s imperative that you have a full understanding of the ramifications of each authentication method.
Watch the video below to learn more!
Marc Linster, Ph.D., is EDB’s Senior Vice President of Product Development and leads EDB’s engineering divisions and product development groups. Marc is committed to EDB being an accelerator to providing architectural “know how” to help customers take advantage of Postgres without significant risk and cost. Marc believes that although new customer adoption of open source is easier than the experience of purchasing proprietary options, tools are still incredibly important, and EDB’s professional services practices provides them. Marc has an extensive background in engineering, technology and logistics with 20 years of management experience. Before joining EDB, Marc spent four years at Polycom, the leading maker of video communications equipment, where most recently he was a Senior Director, Engineering for Cloud and Hosted Solutions. Before Polycom, Marc was Co-founder and President of TriPoint Interactive, a global supply chain consulting and systems integration company. He spent six years at Avicon Group, first as CTO and then as Vice President of Operations. Marc is an avid equestrian. Marc holds a Ph.D. (Dr. rer. nat) in Computer Sciences from the University of Kaiserslautern in Germany.