dimanche 7 juillet 2019

Is there a way to track the context that is hitting inside a java webapp which throws the 403

Getting a 403 for a particular role in web.xml

<security-constraint>
    <display-name>security constraint</display-name>
    <web-resource-collection>
        <web-resource-name>Secured page</web-resource-name>
        <url-pattern>/com/test/</url-pattern>
    </web-resource-collection>
    <auth-constraint>
        <role-name>USER</role-name>
    </auth-constraint>
</security-constraint>

There are series of calls before and when it hits ..../com/test/ (checked in developer tools), webapp returns 403. and works when I user "/com/test/*" .

So I wanted to track the exact context/page/resource it is trying to access. Is there any way to track it from the web.xml perspective ? Not sure if there's any servlet class that I can put a debug point on just before it throws 403.




Aucun commentaire:

Enregistrer un commentaire