Table Of Contents
- 1. History of releases
- 2. Changelog
- 2.1. Changes in version 1.6.0
- 2.2. Changes in version 1.5.4
- 2.3. Changes in version 1.5.3
- 2.4. Changes in version 1.5.2
- 2.5. Changes in version 1.5.1
- 2.6. Changes in version 1.5.0
- 2.7. Changes in version 1.4.4
- 2.8. Changes in version 1.4.3
- 2.9. Changes in version 1.4.2
- 2.10. Changes in version 1.4.1
- 2.11. Changes in version 1.4.0
- 2.12. Changes in version 1.3.1
- 2.13. Changes in version 1.3.0
- 2.14. Changes in version 1.2.1
- 2.15. Changes in version 1.2.0
- 2.16. Changes in version 1.1.4
- 2.17. Changes in version 1.1.3
- 2.18. Changes in version 1.1.2
- 3. Introduction
- 4. Getting started
- 5. pluginv
- 6. AA plugin development
- 6.1. Common configuration options
- 6.2. Plugin development
- 6.2.1. Administrative tasks
- 6.2.2. Basic functionality
- 6.2.3. Pre-defined attributes on self
- 6.2.4. Asking the end-user
- 6.2.5. Using cookies
- 6.2.6. Setting gateway user and groups
- 6.2.7. Setting additional meta data
- 6.2.8. Avoiding costly calculations
- 6.2.9. Adding to the constructor
- 6.2.10. Authentication cache
- 6.2.11. Altering the steps
- 6.3. Plugin response
- 6.4. Connection information
- 6.5. AAPlugin
- 7. MFA Client
- 8. Credential Store plugin development
- 9. Plugin SDK services
- 10. Testing
- 11. Plugin base functions
- 12. About us
- 13. Contacting us
- 14. Technical support resources
Previous topic
8. Credential Store plugin development
Next topic
8.1. Common configuration options¶
The common credential store plugin functionality can be configured by the following configuration options.
New in version 1.4.0. HTTPS proxy configuration can be overridden from plugin config, and password can be stored in a credential store.