As we're using ADFS 2.0 you need to tell the system which organisation you're from (in truth you need to tell the system which AD it needs to ask permissions from) - the initial solution (by far the easiest from a system point of view) was to have the user select either his/her organisation (if they were federated using ADFS 2.0) or a "generic" organisation (basically our AD for those who do not have a federated AD). After some debating we found a solution to present all our customers in an auto-complete input field. Kudos go to the developers for both developing the solution and also for acknowledging that it was a good way to go. Now we only need them to actually tell the users who their local user administrator is based on the organisation they have chosen. I'm told this is no small task, and although I believe this - I still find it strange. I *know* that the information is there. And if we can present the user with a choice of organisations from the same source it shouldn't be witch-craft to conjure up one small matching record from the database.
As we go live we will not have this feature. The out-come will be that users who are not registered will be directed to a customer support page, where they can leave a ticket or call our customer support people. They in turn will have to look into the system and inform the caller who their user administrator is. The customer will then have to contact his local user administrator and ask for access. Talk about a detour just because we can't show a name!
