Multiple SPs problem

[Klingenstein, Nate]

Atul,

> ·         JBOSS EAP Version 6.4 Server with multiple applications(contexts)
> ·         Each context has his own Service Provider(SP) Metadata.
> 
> But this is problematic because of the number of metadata files that are getting generated and to be maintained.

I'll say.

> We are trying to consolidate all the JBOSS contexts to use the same one SAML SP Metadata and Assertion Consumer.

It's up to your SP implementation.  If you can make it look like one SP in metadata and you can make the endpoints the same, then it will look like one SP to the IdP.

> Anyone knows if this is possible? Or have any idea how to accomplished this?

There's a lot of things you could do.

You could make your applications into one application, all protected by the same logical SP at the same location.  You could list multiple endpoints (AssertionConsumerServices) under the same name (entityID).  You could just pipe all this metadata into a single file through any number of means, if that's the only concern.  The simplest way to do that is by literally just appending them to each other, and if you want to get fancy, IdPv3 won't stop you.

I would think about what you want your application to "look like" to the rest of the world and model your implementation on that.  Once you know, you'll be able to answer the question better.  Passing files around is a secondary concern and it can be alleviated in any number of ways.

Take care,
Nate.