Monday, April 29, 2013

p4 sync <> must refer to client <>

I was having the toughest time trying to sync a new folder tree in my depot.

I was getting this error:

//depot/Some-path/some-sub-path/... - must refer to client 'myclient_February29th2012'.

Well, what I was doing wrong was that I was taking the depot path instead of my client path.

So when I did p4 client on the command line it listed my views including this one below:

//Some-path/some-sub-path/... //myclient_February29th2012/Some-path/some-sub-path/...

I updated my p4 sync to use the right side and then the problem went away.

Sometimes, a slight edit can make a world of difference.

Friday, April 19, 2013

OpenID Connect Testing

At my company we are early implementors for bleeding-edge protocols that some of our customers might want to use in an upcoming release.

One of these is OpenID Connect.

OpenID Connect leverages and builds upon OAuth 2.0. It uses the the same authorization server, some of the same endpoints as OAuth 2.0, an access token (in addition to the new id token), and builds upon OAuth use cases like auth code and implicit.

In my testing it seemed simpler to use, less heavyweight, more restrictive in claims/attributes sharing, and used some of latest technologies for its framework: REST, JSON, JWT, JWK, and newer cryptographic libraries like Elliptical curve.