You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For security reasons and to be able to provide more user-specific features to the app, the nyaa API 1.2 will introduce a new way to login. This will be done by a standard OAuth2 Autorization server and a Consent Server.
I'm doing the code for it. The oauth2 api will completely follow the oauth2 standard.
Now that I have implemented the oauth api part on nyaa, I would like which authorization flow should we use? @ltype@xdk78
For example we can either display a a web form from https://nyaa.pantsu.cat/oauth2/auth, let the website handle the login + the grant and then take the token at the end.
Or we can use our own login form and directly send the credentials to the token api url to get the token.
Moreover I would like some ideas on where should we put the API_KEY and API_SECRET (private key) in the code. Since we need to have them available here for travis to compile our releases.
The text was updated successfully, but these errors were encountered:
For security reasons and to be able to provide more user-specific features to the app, the nyaa API 1.2 will introduce a new way to login. This will be done by a standard OAuth2 Autorization server and a Consent Server.
I'm doing the code for it. The oauth2 api will completely follow the oauth2 standard.
The api endpoints will be:
Now that I have implemented the oauth api part on nyaa, I would like which authorization flow should we use? @ltype @xdk78
For example we can either display a a web form from https://nyaa.pantsu.cat/oauth2/auth, let the website handle the login + the grant and then take the token at the end.
Or we can use our own login form and directly send the credentials to the token api url to get the token.
Moreover I would like some ideas on where should we put the API_KEY and API_SECRET (private key) in the code. Since we need to have them available here for travis to compile our releases.
The text was updated successfully, but these errors were encountered: