We have Netscape Messenging Server 4.1.x
Just want to know whether some one has used it's proxy authentication sdk.
The objective is we are using CAS (Central Authentication Service). We want to enable the SSO by having a CAS client in Netscape Server which uses the Netscape proxy authentication sdk.
thanks
> We have Netscape Messenging Server 4.1.x
\
Um, you do know that's been End Of Support Life, for two years, now? That there are security issues that cannot be fixed?
>
> Just want to know whether some one has used it's
> proxy authentication sdk.
No such thing. There is no such SDK.
Yes, we have used proxyauth, and we know what it takes, but .. . .
you should be planning a move from this very, very old platform, not working on doing new things with it..
>
> The objective is we are using CAS (Central
> Authentication Service). We want to enable the SSO by
> having a CAS client in Netscape Server which uses the
> Netscape proxy authentication sdk.
This is very unlikely to be a useful thing for you.I have no idea what CAS might be, nor how you might be able to get it to integrate with Netscape Messaging Server.
Again, proxyauth is not a SKD, nor is it an API. It's a propriatary IMAP extension that we use to allow utilities such as MoveUser to operate.
There are no hooks you can use for SSO that I know of in Messaging 4.x
You should be looking at Messaging 6.2, which does do SSO.
>
> thanks
CAS is the central authentication server.
Yes I agree it is old, but see how are we going to process.
Visit
http://docs.sun.com/source/816-6044-10/security.htm
see the section
Creating Access Filters for HTTP Proxy Authentication
How are we going to proceed is
1 define a Proxy filter
2) above redirect to a java web application
3) invoke the cas client to cross check the issued sso tickets are valid (hand shake)
4) if they are valid use authentication sdk to redirect to netscape mail server
hope there are sdks for Solaris /linux and windows
Also I believe we need to migrate but let us know if you all have found any issues with the above approach
I can only urge you that you should not be attempting to do anyting with this old software. Nobody is likely to be able to help you, and there will be no way to get bugs fixed.
Messaging Server 6.2 uses our Access Manager for SSO authentication. You are building someting we already built for you.
