
Engineer and org chart anomaly @pingidentity. Self-renowned workation photographer. Opinions my own unless plagiarized from someone smarter and/or funnier.
Denver, CO
Joined November 2008
- Tweets8.2K
- Following498
- Followers2.7K
- Likes2.1K
The view from the office was weirdly reminiscent of the view from my hotel room in Moscow circa 2005. Mostly because of the snow, gray skies, and rising steam. But other metaphors are possible too. – at Denver, CO
are links like bsky.app/profile/b--c.bsky.s… still being blocked or algorithmically deprioritized? Been thinking of taking my not posting over to Bluesky rather than not posting here.
Father's Day and some of these children aren't even mine. Also some of mine are missing. Not missing missing, just not present for the adventure at hand.
The Identiverse 2024 Call for Presentations is open (actually been open for a while and I'm late to the game) abstractscorecard.com/cfp/su…
IETF plenary featured a nice memoriam for @vibronet from @rifaat_sy
Set two alarms just in case. Remote attendance at #IETF lets you experience the feeling of being jetlagged without actually flying.
With real jet lag there's at least a chance of some good photo opps flic.kr/p/2dkiCiV but most the likely outcome here is waking up my family in the middle of the night
only cried twice listening to this...
Episode #237 is now available featuring our final conversation with @vibronet. It can be heard at idacpodcast.com and in your podcast app. Vittorio will be missed, but not forgotten.
I wrote a short reflection about working with @vibronet on RFC9470, his recent cancer diagnosis, and the personal importance of unsophisticated humor. pingidentity.com/en/resource…
it was an honor and privilege to share the ride with you my friend
Today the OAuth step up authentication challenge protocol becomes RFC9470.
rfc-editor.org/info/rfc9470
We now have an interoperable way for resource servers to tell clients when the authentication with which the current access token was obtained in insufficient and (crucially) allows the RS to express what requirements would be acceptable… and a way for clients to use that info to influence the next authentication ceremony with the authorization server. Both are obtained with ultrasimple primitives easily added to existing SDKs, achieving sophisticated runtime behaviors without the need for complex eventing systems.
One unexpected benefit of this document is clarity we didn't know we needed. The discussion made clear that we all have different ideas and expectations about what step up authentication really means. The non normative sections of RFC9470 capture the salient point and outcomes of that discussion, hopefully facilitating communications and preempting common errors.
On a personal note. This will be the last spec I drive from idea to RFC in my life, and I couldn't have had a better coauthor than @__b_c . From his world class competence to his encyclopedic knowledge of this space, but above all through his genuine desire for the best outcomes for everyone, Brian is just incredible and a joy to work with. Thank you for this wonderful last ride, dear friend.












