Replies: 1 comment
-
|
I've opened an issue on the AC side for this: aspirepress/AspireCloud#156 The real plan, Mr. Bond, is that API keys are a temporary measure to prevent potential abuse while we're still getting everything "burned in". They'll only be required in the future when an operation needs to be tied to an identity, e.g. if we create an API for leaving reviews. None of the legacy wp.org apis should require a key however. Still, we could initiate login or registration from the client, and basically do it OAuth style:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We need a user friendly way to get the API key from AC into AU (This would need to be extensible to other repos we decided to carry).
As per the original plan AU was supposed to transparently send the domain name to AC na get an API key and automatically fill in the API Key field. Right now it's not possible as AC requires registration.
Is there something better we can do other than just adding a link to the registration page on AC?
Beta Was this translation helpful? Give feedback.
All reactions