© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
keystonemiddleware is automatically already installed and what the customer wants is the auditing side of what keystonemiddleware has. Primarily [1] describes what is required for the autid middleware to be configured. It could be as part of the code python-
In the attempt to get this started, and doing stuff on this, I can point to 2 repos that I worked on [2] is the charm, and [3] is the charmhelpers update. This is my rough idea on how we can go about it.
The key things coming out this piece of work is that we need 3 files changing or adding in each of the major project charms
1. /etc/<project>
2. /etc/<project>
3. /etc/<project>
The sense of these updates can be seen in both [2] and [3]
The api_audit_map.conf file can be taken from the repo in [4], I have not checked to see if they are identical for each of the projects, but this afaik is required for the audit middleware to work
The initial PR created for the charmhelpers also suggested that maybe the audit_middleware context may not be ideal in the IdentityService
There may be other variables that the doc [1] specifies that may be required in api-paste.ini, that may be required for extra functionality
[1] https:/
[2] https:/
[3] https:/
[4] https:/