We are using a ecommerce plataform that can integrate with SAML protocol. They just need the authorization url. Do I need to create an App on One Login?
Or I could user a custom app integration?
Can you provide me some guidelines
What's the platform?
It may already exist in the OneLogin SAML catalog (we have a few thousand apps) but if not, please see https://support.onelogin.com/hc/en-us/articles/202673944-How-to-Use-the-OneLogin-SAML-Test-Connector
Additionally, you (or the Platform vendor) can always contact us to see about getting an official connector added to the catalog if it's not already there.
Regardless, your best bet is OneLogin support as this isn't really a development question.
Related
I hope you can direct me with my query.
I wish to create my own authentication method for users in my Google Apps for Work account. Currently I am using built in Google Authentication, however I wish to build my own authentication method in PHP, Phyton or .NET; language doesn't matter really. So I want users to go to the page I will create, then they will need to pass authentication and be logged to Google Apps.
I know SSO is the way to do it but after my research I found very little about how to achieve it with Google Apps. I mean there is tones of third party platforms like OneLogin etc but I would like to have something I build myself. Ideally I would like to have some examples of SSO which works with GAFW so I could figure out the rest myself. I read somewhere that building own SSO portal it's not a piece of cake and also found an article that you can create something based on oAuth2.0 instead. So tried research about oAuth2.0 but all documentation I found is about authenticating to the application that I build using Google Apps Credentials, where I want the opposite; to be able to access Google Apps using the app that I build.
Hope someone could direct me to some examples or documentation or explain the process of learning curve to get my head around this project of building SSO for GAFW.
If you want to write your own Auth system and become the Identity Provider (IdP), you need to use SAML as that is the only supported method for now.
Here are the step by step instructions
My school is looking to use moodle as an LMS and integrating it with google apps. What I would like to implement in the integration is a single sign on where once a user is logged into google apps, they would immediately be logged into their moodle account. I want this to also be possible vice versa where a user would also be automatically logged into their google apps account if they login to moodle instead. So far the plugins I have found can only do one or the other; not both (or perhaps I do not know how to configure them this way).
I have tried using googleoauth2 and GSAML but had no luck. Can someone please help or guide me somewhere that has this implemented?
Thanks you
THe process is well-documented here: https://docs.moodle.org/29/en/Google_Apps_Integration
The OneLogin plugin (among other options) supports both SSO and Google Apps. I would suggest starting there.
The exact documentation (should you choose to proceed with this login) can be found here. You will need OpenAM as well.
I'm looking to implement Single Sign On for a native iOS app whereby logging in with this single sign on gives the mobile device authenticated access to our private service in a fashion that is somewhat similar to oauth.
The marketing text on openid.net suggests that "OpenID is a safe, faster, and easier way to log in to web sites.". Emphasis on web sites.
So the question is: Is it reasonable to implement openID on a native mobile app, or is openID only for web sites.
I've been scouring the web and I'm not finding a way to fit openID in as my login option.
The best way to do this seems to be to use a UIWebView and render a log in page from your site in it. Once the user logs in, they'll be redirected back to your site and have an auth cookie, which you can extract, store, and send on subsequent HTTP requests to the server.
See this, which has a sample code link at the bottom.
OpenID sends its messages as a series of HTTP requests and responses. Your app and the openid provider must communicate to each other via HTTP post, and you will need to redirect the user to corresponding URLs, and have a URL for the user to be redirected back to. As such, you will probably find it difficult to integrate with your app.
Derek Knight claims to have been experimenting with iOS and OpenID using the Janrain Engage iOS SDK. Although the github link he references no longer exists and he doesnt provide a complete and verified solution, he does offer an idea for how it might work.
OpenID and iOS development - gordonknight.co.uk
Janrain Engage for your iPad Apps
The accepted answer diminish the OpenID protocol. OpenID is a federated authentication protocol aiming simple SSO experience, its a web based protocol but it can be implemented if you design an authentication broker.
APPs share nothing, apps should never access anything but identity token and access token (if allow). here is a link to get you starter in the right path to build seems-less SSO in the mobile between apps regardless the app isolation level.
https://www.pingidentity.com/developer/en/resources/napps-native-app-sso.html
Libraries:
https://github.com/openid/AppAuth-iOS
https://github.com/openid/AppAuth-Android
I have developed asp.net MVC social networking site. I do not want to keep credentials at my database. Its user choice like stackoverflow (this forum). When we saying login the there should be option that to login with google/yahoo/facebook credentials, if user has account over there. What I have to do? is there any webservice provided by sites (google/yahoo/facebook) or what is remedy over this ? this topic in totally new for me . I expecting help from you gems..
You could implement OpenID. DotNetOpenAuth is implementation for .NET.
Sounds like OpenId would work for you (click, and more).
Library's to use in your apps.
For Facebook you want to use Facebook Connect. There is an implementation for .net on codeplex that you may want to have a look at. You may also want to look at this question.
Google uses OpenId. You can use DotNetOpenAuth to connect to google (and any other OpenId provider, such as Yahoo and twitter).
If you want to connect with Microsoft's LiveId, you may want to read this tutorial.
EDIT
There is also the option of using JanRain, a single provider that consolidates a large number of login providers. But note that JanRain is only free up to 1000 users.
There are solutions that enable authentication and features (like status updates, friends etc) from all mentioned sites, one of them is RPX from JanRain. I've experience with RPX personally and it's a great product, however, it will cost you money. They charge you per registered user etc.. I do not know of an open source solution that can compete with RPX.
If you are not interested in paying for a product you can always implement support for the mentioned sites yourself. All of them provide open API's and examples for how to do this. For Facebook it's very easy to implement Facebook Connect. Google and Yahoo both support Open ID and there are plenty of open source resources available for .NET (like http://www.dotnetopenauth.net/).
Good luck with your community!
I am creating a twitter application in iphone using oauth. But my application request for:
oauth_consumer_key,
oauth_signature_method,
oauth_signature,
oauth_timestamp,
oauth_nonce,
oauth_version,
oauth_callback,
Please anyone help me how to create all these keys for my application.
In my twitter account xauth is disabled by default. So, how can I enable it in my application?
It's highly unlikely you need to enable xAuth. The Twitter API documentation, specifically the authentication guide explain these parameters in more detail. Also have the OAuth 1.0 spec open to refer to, even if you're using a third party library- you will save your sanity if you understand the mechanics of the token exchange.
You'll need to read up about OAuth. All the fields are part of the standard. Twitter will give you the first one (oauth_consumer_key), and the version number is always 1.0. (Version 2.0 is not yet complete and Twitter doesn't use it.) The others you need to calculate. Or at least find an open source library that does it for you.
As for enabling xAuth, you need to send a message to Twitter. Sounds like they're getting more and more strict about which apps they allow, though.