openid

OpenID: is the identifier URL unique? what are the differences between the identifiers

泄露秘密 提交于 2019-12-03 15:58:04
问题 In the OpenID specs, it says: Identifier: An Identifier is just a URL. The whole flow of the OpenID Authentication protocol is about proving that an End User is, owns, a URL. Claimed Identifier: An Identifier that the End User says they own, though that has not yet been verified by the Consumer. Verified Identifier: An Identifier that the End User has proven to a Consumer that they own. Identity Provider: Also called "IdP" or "Server". This is the OpenID Authentication server that a Consumer

How do I implement an OpenID consumer in my Google App Engine project?

爱⌒轻易说出口 提交于 2019-12-03 15:46:52
问题 I want to use OpenID in my Java Google App Engine web application but I don't know where to start... I have looked at openid4java and joid. openid4java says you have to place some libraries on the "endorsed libraries"-path. I don't have one locally on my computer, and I sure don't know how to do that on Google App Engine. joid looks simple enough but doesn't look up to date or something because I get a HTTP 400 back from Google when I try to get an authentication. Any pointers? 回答1: http:/

微信授权登录

拜拜、爱过 提交于 2019-12-03 15:32:17
1. 微信登录的两种实现方式   第一种是基于微信公众号进行登录,第二种是基于微信开放平台进行登录。   原因是微信登录不同于QQ登录和微博登录,微信登录没有提供输入账密码登录功能。微信只提供了扫码登录功能,如果是PC端进行登录的话可以用手机进行扫码,但是如果是手机端打开二维码是不能进行扫码的,即便是长按二维码识别功能,但是非常不友好。 2.微信登录的实现方式也有两种   第一种是没有自己的账号体系,直接拉取微信用户信息来进行网站登录。   第二种是有自己的账号体系,授权成功后需要绑定自己的账号。   两种实现方式都可以,只是在向session中存用户信息的时候是存用户获取的微信信息还是根据获取的微信信息(可以根据openID和nickname进行对应查询用户)转换为自己系统内对应的账户信息。 3.基于微信公众号进行授权登录 1.简介   如果用户在微信客户端中访问第三方网页,公众号可以通过微信网页授权机制,来获取用户基本信息,进而实现业务逻辑。 总的来说,分为四部: 1、引导用户进入授权页面同意授权,获取code 2、通过code换取网页授权access_token(与基础支持中的access_token不同) 3、如果需要,开发者可以刷新网页授权access_token,避免过期 4、通过网页授权access_token和openid获取用户基本信息(支持UnionID机制)

OpenID provider on localhost with DotNetOpenAuth

限于喜欢 提交于 2019-12-03 15:01:20
问题 I have the DotNetOpenAuth sample provider running locally and it appears to correctly handle requests via the web browser. I can step through the handler for authorisation in the debugger. I have a project which can authenticate with Google and other providers but fails with the sample provider. The sample provider never sees a request at all and the relying party throws an exception complaining No OpenID endpoint found. Say I do the following in the relying party: string providerURL = "http:

Using OpenID for website Authentication

别说谁变了你拦得住时间么 提交于 2019-12-03 14:37:51
问题 I'd like to implement OpenID in a new application using ASP.NET 2.0 and SQL Server 2005. I chosen Twitter, Facebook and Google as potential OpenID providers. I've found the Twitter implementation in .NET and I was studying Google's OpenID implementation, but I want to make sure that my design is (mostly!) flawless. Is my database schema correct? I've associated a Reader with an ProviderOpenID which contains only a nullable Name column. I store the OauthToken and use that at every request to

OpenID Library for PHP 5.3

不羁岁月 提交于 2019-12-03 13:26:49
问题 Does anyone have openid working in a PHP 5.3 installation? None of the libraries I've tried seem to be working. 回答1: Ok, I finally got to fix the library... I explained everything here (you can also download the php-openid library after my changes). I needed to do what Paul Tarjan suggested but, also, I needed to modify the Auth_OpenID_detectMathLibrary and add the static keyword to a lot of functions. After that It seems to work perfectly although it is not an ideal solution... I think that

OpenID Simple Registration (sreg) vs. Attribute Exchange (ax)

烂漫一生 提交于 2019-12-03 13:02:06
What is the relationship between the OpenID sreg and ax extensions? How does a relying party know which one to request, or both? sreg was written as the Simplest Thing that could Possibly Work, and has a very limited set of fields available. But since that includes nickname , email , and fullname , that's often all you need. Attribute Exchange is much more extensible and featureful, although I suspect in practice features like the update_url and store request have not been widely implemented. As for knowing which to request: In theory, which extensions a provider supports is documented in the

浅析微信支付:商户平台代金券或立减优惠开通、指定用户代金券发放、查询等

眉间皱痕 提交于 2019-12-03 12:27:20
本文是【浅析微信支付】系列文章的第十四篇,主要讲解在如何开通商户平台的代金券或立减优惠功能,商家向指定用户发送代金券,查询发送记录,代金券信息等。 浅析微信支付系列已经更新十四篇了哟~,没有看过的朋友们可以看一下哦。 浅析微信支付:商户平台开通现金红包、指定用户发放、红包记录查询 浅析微信支付:(余额提现)企业付款到微信用户零钱或银行卡账户 浅析微信支付:支付验收示例和验收指引 浅析微信支付:如何使用沙箱环境测试 首先我们需要了解一下什么是代金券和立减优惠? 代金券是微信支付为商家提供的一个营销工具,他的主要功能可以简单理解为商家的满减券,比如常见的“满十减一”、“满x减x”这类,需要用户主动领取或者平台主动为用户发放,核销时会在微信支付调起界面显示优惠券信息。 立减优惠是微信支付为商家提供的另一种自主核销优惠,为何叫自主核销?因为此优惠是一个门槛,不需要用户领取,商家设置一个用户群里,比如全员优惠“满十减一”,那么所有人都可以享受这个优惠,直接在购买商品时自动扣减金额。 以上为简单的解释,下面我会结合官方文档来解释这两个优惠方式。 代金券 微信支付代金券业务是基于微信支付,为了协助商户方便地实现营销优惠措施。针对部分有开发能力的商户,微信支付提供通过API接口实现运营代金券的功能 官方文档地址: https://pay.weixin.qq.com/wiki/doc/api

OpenID Connect lightweight library

大城市里の小女人 提交于 2019-12-03 12:11:26
问题 I'm looking for OpenID Connect (OIDC) Relying Party lightweight library that will have these routines implemented. Compose "Authentication Request" Validate "id_token" signature (including downloading certificate from metadata endpoint) Parse "id_token" JWT The only OIDC flow to be supported is so called " implicit flow " where server answers with "id_token" (and "access_token" if requested) right from authorization endpoint (spec link). Searching over NuGet repository seems to yield the only

Is Google the only OpenID provider that requires “identifier_select”?

走远了吗. 提交于 2019-12-03 11:49:05
问题 I am developing an OpenID consumer in PHP and am using the fantastic LightOpenID library (http://gitorious.org/lightopenid). Basing my code off of that found in the example client script I have successfully created a consumer. However, I've run across a snag: Google requires the openid.identity and openid.claimed_id to be set to "http://specs.openid.net/auth/2.0/identifier_select" (see here). If I do that it works but other providers (i.e. AOL) don't. Here are my questions: Is Google a corner