- First up this week, on the OpenSSO Users mailing list, we had an interesting email from Romanov Vladimir, of the R&D department of Russian telecommunications operator Scartel, saying that they are using OpenSSO as the authentication mechanism for their new Yota WiMax network. We’re looking forward to hearing more as they move Yota from test mode into production.
- Staying in Eastern Europe, I noticed the work going on at the Budapest University of Technology and Economics (BME), where they are also using OpenSSO for authentication – a nice diagram and some information on the architecture; unfortunately, Google Translate doesn’t yet stretch to Hungarian, although Adam Lantos of HME (a regular participant on the mailing list) says he’ll send some information in English soon.
- Finally, Mike Hortobagyi, up in Canada, writes today about an experiment I ran last night, deploying OpenSSO onto GlassFish+OpenSolaris at Amazon EC2. Logically, it all should work ok, but it’s great to try something like this and see it actually running up in the cloud. It took me less than 45 minutes to get OpenSSO and the Fedlet running, including uploading the OpenSSO WAR file to the EC2 instance. I’ll leave the instance up for a few days so you can go play – try out the Fedlet (click the link to login, username demo, password changeit), or even the federation validator (same username/password). NOTE – it’s a little confusing, since I gave OpenSSO and the Fedlet the same hostname, but they are independent web applications, with no shared state. You can see all the gory SAML details (WoooOOOooo! Spooky!) in the Fedlet page after you login. Go give it a try; if you get a host not found, or page not found, error, I’ve likely taken the instance down… I can’t keep paying $0.10 per hour forever, you know! 😉
So, there you go – I managed to squeeze in a spooky reference in the end… Happy Halloween, everyone!