janrain

Janrain OpenId vs lightopenid PHP libraries

别来无恙 提交于 2019-12-23 21:12:11
问题 What are the differences between the PHP implementation of Janrain's PHP OpenID library and the LightOpenID. Is one more secure than the other? According to Google's best practices page: A correct OpenID implementation has to: cover checking of cryptographic signatures checking of nonces Yadis discovery I'm guessing the Janrain's library does fulfill all these requirements as Google recommends the library, but is the LightOpenID fulfilling 1 & 2. 回答1: LightOpenID uses the stateless version of

Not logged in after manual login in CakePHP if redirected, logged in if no redirect

梦想与她 提交于 2019-12-23 04:46:10
问题 I'm using Janrain engage to login to my CakePHP site, and when handling the user data, I want to automatically login using the $this->Auth->login()-function. I manage to login fine if I don't redirect after the call, but if I redirect, I'm not logged in. Does anyone now why or what I can do to straigten this? function janrain(){ $rpxApiKey = 'kassdkfkafkkadskfkkdfkksdk'; if(isset($_POST['token'])) { /* STEP 1: Extract token POST parameter */ $token = $_POST['token']; /* STEP 2: Use the token

Janrain RPXnow (Engage) (https://rpxnow.com/) bypasses popup-blockers… how?

删除回忆录丶 提交于 2019-12-11 04:57:28
问题 Basically I need to open a login window in a popup, so that it doesn't get blocked by popup blocker. Similar to what Janrain does in it's RPXnow solution. How do they do that? 回答1: Most pop-up blockers allow pop-ups that were triggered by a user action, e.g. clicking on one of the login links on the page you linked to. So if you tie your login popup to a login button that the user has to click to open it then it ought to get past the blockers OK. (or am I missing the point - were there other

user_signed_in? always returns false

走远了吗. 提交于 2019-12-10 15:37:45
问题 I have been following these railscasts http://railscasts.com/episodes/209-introducing-devise && http://railscasts.com/episodes/233-engage-with-devise for user authentication, however whenever I try to see if a user is signed in, the response is always false. I tried a bunch of things to try remediating this issue. I tried different versions of devise and devise_rpx_connectable. I tried changing settings around in the configuration file. I tried running 'rails generate devise:install' a bunch

Read Json data response using php [closed]

自作多情 提交于 2019-12-07 15:02:17
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 6 years ago . How can I read a JSON data response using php? The response t comes after user authentication done from a third party. Primarily, I just want displayName and preferredUsername data. Json response: { "stat": "ok", "profile": { "providerName": "testing", "identifier": "http://testing.com/58263223", "displayName":

JanRain OpenID in PHP SREG?

南楼画角 提交于 2019-12-06 08:53:00
问题 I setup the demo with a modified login I found called open-id selector. the login works fine and the identity url comes back, but the SREG data I ask for is never populated, required or optional. I am logging into my page with a gmail account. Here is the code from my try_auth.php that I edited $sreg_request = Auth_OpenID_SRegRequest::build( // Required array('email'), // Optional array('fullname', 'gender', 'timezone', 'dob', 'country')); what gives? 回答1: Google's OpenID identity provider

Read Json data response using php [closed]

末鹿安然 提交于 2019-12-06 01:37:53
Closed. This question is off-topic . It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 6 years ago . How can I read a JSON data response using php? The response t comes after user authentication done from a third party. Primarily, I just want displayName and preferredUsername data. Json response: { "stat": "ok", "profile": { "providerName": "testing", "identifier": "http://testing.com/58263223", "displayName": "testing", "preferredUsername": "testing", "name": { "formatted": "testing" }, "url": "http://testing

JanRain OpenID in PHP SREG?

半腔热情 提交于 2019-12-04 11:58:39
I setup the demo with a modified login I found called open-id selector. the login works fine and the identity url comes back, but the SREG data I ask for is never populated, required or optional. I am logging into my page with a gmail account. Here is the code from my try_auth.php that I edited $sreg_request = Auth_OpenID_SRegRequest::build( // Required array('email'), // Optional array('fullname', 'gender', 'timezone', 'dob', 'country')); what gives? Google's OpenID identity provider doesn't support SREG. Instead, they support OpenID Attribute Exchange for limited attributes (username and e

Janrain's PHP-OpenID and Google/Yahoo

穿精又带淫゛_ 提交于 2019-11-28 20:51:25
I'm using Janrain's PHP-OpenID 2.1.3 , and I've managed to get it working with all the providers I have tried except for Google and Yahoo. The major difference here seems to be that Google and Yahoo, unlike most other providers, don't use a user-specific URL, but rather have the user discovery framework all on their end - which throws the default Janrain framework for a loop then it tries to begin the auth request. From what I've seen it looks like it's probably the YADIS discovery that is throwing the error, which should be able to be bypassed since the discovery is on Google or Yahoo's end,

php-openID doesn't work with Yahoo

 ̄綄美尐妖づ 提交于 2019-11-28 11:18:27
i am trying to use php-openid library for implementing openID in my site. the basic consumer example inside its package doesn't work for Google and Yahoo. i found the Google solution here: Example usage of AX in PHP OpenID but it doesn't still work for Yahoo! . how can i made it works? wow it is solved now !!!!! i traced the functions and found the problem.and that is.... in "try_auth.php" file i used "$attribute[] = Auth_OpenID_AX_AttrInfo::make('http://axschema.org/contact/email',2,1, 'email');" for getting the user email from provider. it works fine in Google because Google ignore '2'