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. 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] as: > [email protected] > To unsubscribe, change settings or access archives, see > 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
