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

can't authenticate oracle account anymore #56

Closed
aaronedell opened this issue Aug 24, 2016 · 7 comments
Closed

can't authenticate oracle account anymore #56

aaronedell opened this issue Aug 24, 2016 · 7 comments

Comments

@aaronedell
Copy link

This used to work. But stopped working.
image

@aaronedell
Copy link
Author

I know these credentials are correct

@aaronedell
Copy link
Author

the problem is the storage- isn't required for one type of Oracle account. See these two oracle account API endpoints:
https://storage-a422618.storage.oraclecloud.com/v1/storage-a422618
https://usoraclegm1.storage.oraclecloud.com/v1/Storage-usoraclegm1

@matryer
Copy link
Contributor

matryer commented Aug 24, 2016

I think the solution is to add Endpoint configuration and let them specify the full URL instead of trying to be clever and build it.

Endpoint URL: https://whatever.storage.oraclecloud.com/auth/v1.0

@matryer
Copy link
Contributor

matryer commented Aug 24, 2016

@Xercoy can you look at this?

@Xercoy
Copy link
Contributor

Xercoy commented Aug 24, 2016

There are two different types of storage subscriptions which have different endpoint conventions. The metered subscription includes the storage- prefix at the end, it's the first endpoint @aaronedell mentioned. The unmetered subscription is the second endpoint. The implementation that was merged only works for metered. See here for more info.

One simple solution what @matryer mentioned: having the auth endpoint field in the config. That was how I originally did it, but I was annoyed at how unfriendly that was. The only way the auth url can be obtained is by reference from the dev documentation + mangling information included int he endpoint.

Another solution I thought of was having a dropdown list for the user to specify whether the account is of the metered or unmetered type. We could then be clever and format the auth endpoint for both subscription types... I didn't want to go on this route because of how much the frontend work would have delayed a merge.

I'll work on a fix to modify the implementation so that both subscriptions types are compatible with stow.

@aaronedell
Copy link
Author

thanks Corey

@matryer
Copy link
Contributor

matryer commented Aug 26, 2016

Is this fixed now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants