{"repo":"labd/django-iam-dbauth","free":true,"listed":false,"github":"https://github.com/labd/django-iam-dbauth","clone":"git clone https://github.com/labd/django-iam-dbauth.git","description":"Django backends to support IAM database authentication for AWS","language":"Python","stars":49,"topics":["django","aws","postgresql","iam","rds-iam-authentication","python"],"license":"MIT","category":"databases-storage","readme_excerpt":"Django IAM database backends Usage In your settings use the following SSL and PostgreSQL When using IAM authentication with RDS, SSL is required. If it's not used, such as when using a CNAME (see below), login will be denied with the below error: SSL and MySQL Acquired Token won't work with MySQL if use RDS instance name, which is a CNAME record, as a HOST, because by default it will be resolved to a cannonical name by django-iam-dbauth. As a result the hostname of the token will bi different. To prevent the module from resolving CNAME, set \"resolve cname enabled\" to False. CNAME considerations Currently, IAM authentication is not supported with CNAMEs. However, this package does CNAME resolution so that the signed request for a password will work. The issue with this approach is that from the DB library's point of view, the connection is initiated to the hostname as defined in the settings. If using SSL, certificate verification will fail. In this case, for PostgreSQL you may want to set sslmode to require or verify-ca . Further documentation: PostgreSQL SSL modes AWS guide on IAM DB authentication","default_branch":null,"files":null,"tree":[],"storefront":"/r/labd","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/labd/django-iam-dbauth/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}