After setting the Consent page and enabling Google+ API,
when I try to get credentials for this API there is no option to choose Google+ API on the "Add credentials to your project" page.
Do you have the same problem in the meanwhile or I have to do something else?
That scenario has been expired.
Now I found out that I have to just create an OAuth Client ID
Select my application type, add my Authorized JavaScript origins, and Authorized redirect URIs manually.
"Authorized JavaScript origins" are your application base domains that you want to implement external login Js library like
<script src="https://apis.google.com/js/platform.js" async defer></script>
"Authorized redirect URIs" are the pages that you want to redirect the user after login
Related
I want to implement oAuth2 flow in my Slack app, but it's impossible to test properly.
I have added /slack/redirect-url as a redirect URL on my App management page. Then try to install\reinstall the app on the following page:
Unfortunately, it doesn't work, my endpoint isn't called.
However, if I go to the "Distribution" section and try to install the app from there it does call my redirect URL:
So, what's the issue? Why the first approach doesn't call my redirect URL, but the second one does? Am I missing something fundamental?
The "Reinstall App" button will handle the entire exchange of verifying and granting the OAuth token within Slack, so there is no need for the redirect.
The redirect URL is intended for users who are authenticating with your service, and thus you need to store the token.
User clicks the install button
User authorizes through Slack UI
Slack redirects to your desired URL
You grab the code included in the redirect call
You exchange the code for the OAuth token
You store the OAuth token
When you use the "Reinstall App" button in your app management view, steps 3-6 are handled entirely by Slack and the token is displayed to you.
To properly test the redirect URL, you can go through the OAuth flow manually. Given that they're simply GET requests, you can just modify the links and paste directly into your browser.
Step 1: Authorize the app – this will send you to Slack for authorization, and then your redirect
https://slack.com/oauth/authorize?client_id=CLIENT_ID&scope=SCOPES&redirect_uri=REDIRECT_URI
Step 2: Exchange the verification code for OAuth token
https://slack.com/api/oauth.access?client_id=CLIENT_ID&client_secret=CLIENT_SECRET&redirect_uri=REDIRECT_URI&code=CODE
I have integrated Login with Yahoo in our application using Oauth2.0 authorization code flow which is working fine. Once user is login using this option and user profile information extracted, I want to logout user from Yahoo as user is not aware that they have Yahoo session active. I dont not see any Yahoo Logout API or Javascript or URL to use in our application. Yahoo logout URL is not unique and needs crumb value for each logout in the url.
https://login.yahoo.com/config/login/?logout_all=1&.crumb=yQBVhxADZpA&.direct=2&.done=https%3A%2F%2Fwww.yahoo.com
Please let me know if there is any standard Yahoo logout approach.
I've added the client id and secret to the yml configuration file, but it's not working. When I try to login with one of the providers, it redirects me to a blank page with the message 'cannot POST /signin/google', if I try to login with Google, for example. I generated a monolith application with JWT authentication and social login feature (I'm using Angular 2+).
Maybe you should check https://console.developers.google.com/apis/credentials and set properly your Authorised JavaScript origins and Authorised redirect URIs. First one should be set to just for example http://localhost and second one must contain several entries for example
http://localhost:8080
http://localhost:8080/signin
http://localhost:8080/signin/google
We have a spa (Angular 2) that we are trying to integrate with okta. I created an app in okta with SWA sign on method. I click on the app and it redirects me to my spa app as expected.
However, I do not see and information being passed on the redirect. How do I validate that the login was successful? Is there some token info that I can validate? Something else?
Thanks!
The SWA sign on method depends on the Okta plugin - do you have it installed? If so, when you hit your login page (and the origin matches the url you've configured in the app), the plugin will try to inject the creds into the login form. It uses a heuristic to figure out which fields to inject into, so ideally your login page will look like a standard login form (i.e. text field for username, password field for password, and a login button).
There are other template apps you can use if you don't want to depend on the plugin being installed (not sure about your setup) - for example, "Template App" will post the credentials to an endpoint (although this is usually not an option since most apps will want to add an XSRF token to their login forms).
I am using Spring Security to authenticate with SAML and Okta, generally it works, I am able to authenticate a user and access secured URLs within my application. So far so good.
Now I have a requirement for a special type of 'internal' users to use different authentication mechanism (those users will not be in AD nor Okta) - so if authentication fails using Okta I want to display different login page. Problem is that I am unable to redirect from Okta login page to my custom page after unsuccessful login, seems like Okta will not redirect even after many unsuccessful attempts.
Is there a way to implement such requirement?
You can't redirect Okta on a failed authentication. You will need to determine what type of authentication to use prior to validating the username and password. Okta supports application based custom login page and so when the user tries to access the application, Okta redirects to your login page. From there your login page will determine where to authenticate the user.
Okta configuration for custom login page
You can use Okta's Authentication APIs and SDKs to authenticate against AD and custom code.