Hi Phil, The ADFS side should be fine. The concern is what version of CAS Server is associated with Luminis 5? The cas-server-support-wsfederation uses a new version of openSAML which was upgraded in 3.5.1, I think. If the version is older it is not likely going to work because of the dependency issues. Luminis 5 (.0) shipped with an older CAS Server build, if memory serves, but later Luminis updates may have fixed that.
What issues are you seeing? On 1/9/15 12:17 PM, [email protected] wrote: > I'm attempting to go the other way - put ADFS 3.0 in front of CAS. > > John - are you aware of any oddities in ADFS 3.0 that would prevent > your solution at > https://github.com/Unicon/cas-adfs-integration/wiki/cas-server-support-wsfederation > from working? Any or do you have any updates to this solution? > > I'm attempting to implement it on the CAS server shipped with the > Luminis 5 portal and am hitting some errors. Just wanted to check to > see if it's likely me or something in ADFS 3. > > Thanks for your work on this solution! > > Phil > > > On Thursday, December 18, 2014 at 11:50:57 AM UTC-5, John Gasper wrote: > > I haven't attempted to CASify ADFS 3.0, but hopefully this will help. > All of the .cs files are embedded as string in one of the dlls. I > found > a reference online to such and I believe I recall confirming that > to be > the case. You can use Visual Studio to copy the "strings" (i.e. > files) > out modify them and slip them back in. > > You'll likely need a modified .NET CAS Client because of the way the > client generates the proxy callback URL (I'm assuming that you'll use > ClearPass). The client builds the callback url by appending the > querystring of the first request that hits it after start up. This > basically makes for a dynamic callback URL that will require > continual > changing on the ClearPass config side. > > I believe line that needs to be fixed/cut is > > https://github.com/Jasig/dotnet-cas-client/blob/master/DotNetCasClient/Utils/UrlUtil.cs#L101 > > <https://github.com/Jasig/dotnet-cas-client/blob/master/DotNetCasClient/Utils/UrlUtil.cs#L101>. > > I happen to have just looked this up for a client that was trying > to do > the same thing. They ultimately decided to use Shibboleth to > bridge CAS > and ADFS as it required very little to no mods of ADFS to work, and > CASifying ADFS directly has issues in load balanced ADFS clusters. > > Good luck. > > On 12/18/14 6:57 AM, Kenneth Erard wrote: > > Hello, > > > > I'm implementing ADFS 2012 R2 (ADFS 3.0) for Office 365. I'm > > interested in CASifying it, but it looks like it has been changed a > > great deal from ADFS 2.x with respect to customizability. The > entire > > service appears to be contained in DLLs, IIS is no longer > installed, > > and Microsoft recommends using Powershell to make limited supported > > customizations. > > > > Has anyone on the list successfully CASified this new version of > ADFS? > > -- > > You are currently subscribed to [email protected] > <javascript:> as: [email protected] <javascript:> > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > <http://www.ja-sig.org/wiki/display/JSG/cas-user> > > > > -- > You are currently subscribed to [email protected] > <javascript:> as: [email protected] <javascript:> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > <http://www.ja-sig.org/wiki/display/JSG/cas-user> > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
