[Openid-specs-ab] OpenID Connect Launch Commencement
Allen Tom
allentomdude at gmail.com
Tue Jul 19 04:17:49 UTC 2011
Hi Eric -
Is the demo working? It seems to be printing out some errors when I try it.
Traceback (most recent call last):
File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/__init__.py",
line 700, in __call__
handler.get(*groups)
File "/base/data/home/apps/s~oauthssodemo/1.351921969630720495/index.py",
line 96, in get
session = sessions.Session()
File "/base/data/home/apps/s~oauthssodemo/1.351921969630720495/appengine_utilities/sessions.py",
line 562, in __init__
self.session = _AppEngineUtilities_Session.get_session(self)
File "/base/data/home/apps/s~oauthssodemo/1.351921969630720495/appengine_utilities/sessions.py",
line 142, in get_session
ds_session = db.get(str(session_key))
File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py",
line 1473, in get
return get_async(keys, **kwargs).get_result()
File "/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py",
line 1432, in get_async
keys, multiple = datastore.NormalizeAndTypeCheckKeys(keys)
File "/base/python_runtime/python_lib/versions/1/google/appengine/api/datastore.py",
line 180, in NormalizeAndTypeCheckKeys
keys = [_GetCompleteKeyOrError(key) for key in keys]
File "/base/python_runtime/python_lib/versions/1/google/appengine/api/datastore.py",
line 2409, in _GetCompleteKeyOrError
key = Key(arg)
File "/base/python_runtime/python_lib/versions/1/google/appengine/api/datastore_types.py",
line 364, in __init__
raise datastore_errors.BadKeyError('Invalid string key %s.' % encoded)
BadKeyError: Invalid string key
ag5zfm9hdXRoc3NvZGVtb3IiCxIbX0FwcEVuZ2luZVV0aWxpdGllc19TZXNzaW9uGME=.
On Sun, Jul 17, 2011 at 8:58 AM, Eric Sachs <esachs at google.com> wrote:
> >> Contacting friendly developers to begin implementations and feedback
> based upon their implementation work
>
> Google's OpenIDConnect endpoint is now live in production, and we have a
> sample RP that shows the code required to use it at:
>
> http://oauthssodemo.appspot.com/step/1
>
> We have sent the config details for our endpoint to a few
> developers/vendors to let them start integrating with it, though we are not
> trying to formally announce it's availability at this time.
>
> We will show it at the workshops Google is running Monday & Tuesday
> afternoon. The presenters at the Tuesday OIDF summit can use it as well if
> it helps.
>
>
> On Thu, Jul 7, 2011 at 11:11 PM, Mike Jones <Michael.Jones at microsoft.com>wrote:
>
>> At this point we are ready to begin the OpenID Connect launch. Don,
>> should we have a planning call among the launch owners in the next few days
>> to plan the rollout steps?****
>>
>> ** **
>>
>> Steps we’re already taking:****
>>
>> **· **Contacting friendly developers to begin implementations and
>> feedback based upon their implementation work****
>>
>> **· **Write a one-page overview of the OpenID Connect specs.
>> (Pamela Dingle has volunteered to write this by tomorrow/Friday.)****
>>
>> Steps we should take soon:****
>>
>> **· **Add links to Connect specs from
>> http://openid.net/developers/specs/. (Mike to investigate.)****
>>
>> **· **Update content on openidconnect.com to refer to the actual
>> OpenID Connect specs, archiving the previous proposal. (John Bradley
>> already owns this.)****
>>
>> **· **Send a note like the one below to specs at openid.net and
>> board at openid.net and posted on OpenID blog announcing this milestone.
>> (Allen, do you want to be the one to do this? I assume we should wait for
>> the overview document to be posted before doing this?)****
>>
>> ** **
>>
>> Any other thoughts or suggestions?****
>>
>> ** **
>>
>> -- Mike****
>>
>> ** **
>>
>> *From:* Mike Jones
>> *Sent:* Thursday, July 07, 2011 2:12 PM
>> *To:* openid-specs-ab at lists.openid.net; board-private at openid.net
>> *Subject:* Functionally complete set of OpenID Connect specs****
>>
>> ** **
>>
>> I’m pleased to announce the release of a functionally complete set of
>> OpenID Connect specifications. Remaining edits should consist of
>> corrections, clarifications, and reorganization, rather than additions of
>> significant new functionality. As such, these should now be ready for early
>> feedback from and implementation by friendly developers. The specs are:*
>> ***
>>
>> ** **
>>
>> OpenID Connect Core:
>> http://openid.net/specs/openid-connect-core-1_0.html****
>>
>> OpenID Connect UserInfo:
>> http://openid.net/specs/openid-connect-userinfo-1_0.html****
>>
>> OpenID Connect HTTP Redirect Binding:
>> http://openid.net/specs/openid-connect-http-redirect-1_0.html****
>>
>> OpenID Connect Discovery:
>> http://openid.net/specs/openid-connect-discovery-1_0.html****
>>
>> OpenID Connect Dynamic Client Registration:
>> http://openid.net/specs/openid-connect-registration-1_0.html****
>>
>> OpenID Connect Session Management:
>> http://openid.net/specs/openid-connect-session-1_0.html****
>>
>> OpenID Connect Framework:
>> http://openid.net/specs/openid-connect-framework-1_0.html****
>>
>> ** **
>>
>> All are in SubVersion at
>> http://svn.openid.net/repos/specifications/connect/1.0/.****
>>
>> ** **
>>
>> -- Mike**
>> **
>>
>> ** **
>>
>
>
>
> --
> Eric Sachs | Senior Product Manager | esachs at google.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20110718/1f4607ab/attachment.html>
More information about the Openid-specs-ab
mailing list