We’re working on a SSO solution that allows users to log in via .net and then end up at a PHP app. I’m working on the PHP end, and after much work, I’ve decoded, parsed, and otherwise done things to the cookie that .net sets with the username and ticket expiration date.
At least I think I have. My difficulty now is that the .net developer is too busy right now to set up a test login page that generates these cookies so I can truly test. What I’m wondering is how long setting up this test page should take. My feeling is that it shouldn’t take long, but then I’ve never done it. (Heaven forbid that I be like a client who tells a developer that ‘it should only take an hour or so.’)
I just want to know what I should reasonably be able to expect. Simple log in that creates a formsauth ticket and sends the logged in user over to my test page. FWIW, they already have any number of log in pages set up for .net apps that are currently in use.
EDIT: To clarify, I’m not going to be implementing this. I want to know how long it should take the .net developer to do so.
Here is a walkthrough of the configuration side for Forms authentication in ASP.NET. If you can code a two-textbox page and a button on a web form, then you can do the rest. I would budget two hours if you never do any ASP.NET whatsoever.