JWT Decoder - In-App Payments — Google Developers
JWTをデコードしてくれる
OnStar is opening its API to select devs to create new apps utilizing the system’s Advanced Telematics Operating System (ATOM).
To be clear, OnStar’s API is still closed, but GM’s telematics service will accept applications from developers and based on what they submit, will then grant them access to OnStar’s 1s and 0s.
So what can we expect to see? Not much until OnStar opens the doors in the first half of this year. But it has announced a partnership with RelayRides, a peer-to-peer car-sharing service that lets owners of OnStar-equipped vehicles to rent out their rides when they’re not being used. By using the OnStar API, RelayRides will be able to approve a vehicle for use and then using an iPhone or Android app, the renter can unlock the doors to a vehicle that’s been reserved in advance.
Twitter uses OAuth to authorize access to individual data. This video screencast shows how to use OAuth and Twitter from within the Kynetx Rule Language (KRL).
romeda@gmail
Webfinger example
A Proud World First Moment for FundRazr « ConnectionPoint Systems Inc
Adaptive Accounts API in Action
OpenID authentication request parameters to an active client
Google Hybrid Protocol Demo (OpenID + OAuth)
メールアドレス, 言語, Google ドキュメント, Google コンタクト
New OpenIDs can be added on the fly, by picking one from a list suggested by the site, or by typing the provider’s URL.
I made a little demo that shows what John described (using OTPs in password
backed cards):
http://www.otpcarddemo.comYou can get a managed “OTPCard” there. Every time you want to use the card
(or preview its claim values), you have to go back to the above site and
request an OTP.
I tested it with Cardspace, Azigo and the Higgins iPhone Selector. Not
really sure what the demo proves, but I thought it would be an interesting
exercise to try and implement this with existing technology.
Page 1 of 3
