Rich wrote: >>Is it forcing the login through the 'normal' browser password mechanism? >> >> > No, I'm using an authenticated bind to a secure LDAP server as the > underlying mechanism. For the security part (but see below)
OK >>The fact that it was generated from a cgi should not be a factor. >> >> > That's what I thought at first glance too but now I'm not so sure. I'm > starting to think that the permissions the applet picks up are different > depending on if the page gets loaded from a direct URL versus those > acquired when a page is written back to the user from the perl CGI > module. Is that possible? I suppose it is possible ... I don't think I have ever tried it ... seems very unlikely to me ... but if you have empirical evidence ... > If you are unable to confirm this behaviour I could spend some time to > convert the existing script into a generic one to illustrate the problem > (who knows, doing so might even solve it <g>). I cannot look into it today. Miguel ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
