-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add support for MFA #6
Comments
Thanks for filing this feature request @flippyboy. I was able to reproduce this issue, it's indeed happening on MFA enabled accounts. I will try to find some time the enxt days to work on that. |
In an ideal world a user would be able to request an API via customer connect, in the same way that they can on network.pivotal.io. This would negate the need for any username or password to be used by vcc. That said I think we'd have to demonstrate signifficant use of vcc to justify the customer connect team doing this work. |
I just found out that Customer Connect has the possibility to use an authentication code instead of username + password. |
Very interesting, thanks @flippyboy. I'll add this to the backlog, as would hopefully simplify things quite a bit on our side. |
When trying to log in using an MFA enabled account, I get the following reply:
Logging in... &{%!e(string=could not find node that matches "input[name=\"SAMLResponse\"]")}
I'm guessing this is because I have MFA enabled on my account.
As MFA is something that everyone should have enabled on their accounts, it would be nice to support it here.
The text was updated successfully, but these errors were encountered: