Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

insecure=True should be set under keystone_authtoken section of dmapi.conf #130

Open
MuralidharB opened this issue Oct 19, 2018 · 2 comments
Assignees
Labels
Resolved Resolved the issue but not verified by the reporter

Comments

@MuralidharB
Copy link
Contributor

The default value should be set to insecure=True in dmapi.conf template. User can override this value and supply certificate if they like to.

@MuralidharB MuralidharB changed the title insecure=True should be set under kestone_authtoken section of dmapi.conf insecure=True should be set under keystone_authtoken section of dmapi.conf Oct 19, 2018
@abhijeetpatra abhijeetpatra self-assigned this Oct 22, 2018
abhijeetpatra added a commit to abhijeetpatra/triliovault-cfg-scripts that referenced this issue Oct 22, 2018
- Added 'insecure' option in the template file.
- Added/modified 'debug' , 'Region Name' and 'ca_file' as well.
@abhijeetpatra
Copy link
Contributor

PR #131 resolves this issue.

1 similar comment
@abhijeetpatra
Copy link
Contributor

PR #131 resolves this issue.

@abhijeetpatra abhijeetpatra added the Resolved Resolved the issue but not verified by the reporter label Oct 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolved Resolved the issue but not verified by the reporter
Projects
None yet
Development

No branches or pull requests

2 participants