Hi,
i'm a complete newbie to many of the topics in my question so for that i do apologise. In the absence of an architect familiar with portal / security / web design i've been asked to give a brief overview of what UAG / FIM is in relation to my organization building a portal (to be used by 'external' users to access various functionality such as interacting with workflow steps, submitting files, receiving documents etc.). For workflow I have suggested a product, and pointed out that we would need developement time to set up a suite of workflows on said product. We would also need to allow for installation / setup of said product. For the portal itself, i'm envisaging a website onto which users can log on and once logged on can browse to whatever area they need to use. What i'm not clear on is what UAG / FIM's role in this is. If the website was developed in, say, ASP.Net woudl it be a case of the ASP.Net code calling UAG / FIM at the logon screen to authenticate? Or would UAG / FIM provide a wizard to build a logon page or...what?
Thanks!!!