Hello, first post here, thanks in advance for any feedback.
I am evaluating Apache CXF Fediz as a way to create a Tomcat 6 relying party for ADFS 2.0.
I did the configuration steps, built the simple web app (no spring) example and first tried to access the medata URL. Got a no such class exception when trying to get the servlet context. Then, I tried building the tomcat plugin and noticed it has a dependency on the Tomcat 7 API.
So, the obvious questions is whether the plugin can be run on Tomcat 6. Can any previous experience be leveraged before I start tweaking a plugin version for Tomcat 6 API?
Also, a rough sample of fediz_config.xml for ADFS would be highly appreciated. I have experience in configuring the ADFS and Shibboleth world, but a bit stuck in Fediz at the moment :)
Regards,
/Domenec
PS: I know it may sound exotic, but the goal is to write a login handler for Shibboleth that uses an existing SSO session in ADFS. ADFS can proxy claims from Shibboleth to its MS relying parties, but not the opposite. Because of organizational decisions, ADFS must remain the login point (yes I know that letting users log in Shibboleth there would be no issues, I tested that). Inspiration comes from Shib wiki where login handlers using CAS are provided.
I am evaluating Apache CXF Fediz as a way to create a Tomcat 6 relying party for ADFS 2.0.
I did the configuration steps, built the simple web app (no spring) example and first tried to access the medata URL. Got a no such class exception when trying to get the servlet context. Then, I tried building the tomcat plugin and noticed it has a dependency on the Tomcat 7 API.
So, the obvious questions is whether the plugin can be run on Tomcat 6. Can any previous experience be leveraged before I start tweaking a plugin version for Tomcat 6 API?
Also, a rough sample of fediz_config.xml for ADFS would be highly appreciated. I have experience in configuring the ADFS and Shibboleth world, but a bit stuck in Fediz at the moment :)
Regards,
/Domenec
PS: I know it may sound exotic, but the goal is to write a login handler for Shibboleth that uses an existing SSO session in ADFS. ADFS can proxy claims from Shibboleth to its MS relying parties, but not the opposite. Because of organizational decisions, ADFS must remain the login point (yes I know that letting users log in Shibboleth there would be no issues, I tested that). Inspiration comes from Shib wiki where login handlers using CAS are provided.