Fletcher Cocquyt <[email protected]> writes: > The cap developers reported this error this morning and said it started > logging 7/27
> http://med.stanford.edu/profiles/intranet/visiblityDialog.css > "HTTP Status 403 - The request URL is not WebAuth-guarded and no > WebAuth-guarded login page has been specified." > does anyone know if this can characterized as app or KDC otherwise? I don't recognize that error message; it's at least not part of the standard WebAuth code base. It might be generated by the contributed Java WebAuth implementation -- I'm not sure, since I've not used it. Or it might be an internal error thrown by their application. The error is originating from inside Tomcat, so it's something in the Java code. -- Russ Allbery <[email protected]> Technical Lead, ITS Infrastructure Delivery Group, Stanford University
