Running two ADFS (SSO) products in parallel?

[gshaw]

Bit of a weird one this so not sure if anyone else has done something similar, maybe @EduTech may be able to advise?

 

We're currently using the free version of Centrify Identity Service to provide SSO functionality for Office 365. It works fine for that and we've been happy with it but recently some other cloud \ hosted apps that we're implementing all show steps for ADFS in their authentication instructions.

 

Unfortunately those steps don't map like-for-like on Centrify and it'll cost us £££ to get them to build custom app definitions, which also means going onto a paid plan as well. On top of that some of the vendors won't support using a different product to ADFS (although in theory they're all using WS-Fed \ SAML at the end of the day) and we don't want to open ourselves up to being stuck in the middle of two vendors if something doesn't work.

 

With that in mind I'm thinking of setting up ADFS but what I'm wondering is if I can leave Office 365 where it is and just point the new apps at the freshly built ADFS URL when it's done? In theory I think it should work as you define the SSO URL when setting up each application but not certain if there's something at a domain level that might clash at some point?

 

The only reference to something similar is where someone had a badly-configured ADFS server they wanted to move away from and the gist was that it was OK to build a new one in-situ for the new application - has anyone been in a similar situation?

Edited June 29, 2015 by gshaw