You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: openam-radius/openam-radius-server/src/main/java/org/forgerock/openam/radius/server/spi/handlers/OpenAMAuthHandler.java
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -115,9 +115,9 @@
115
115
* </pre>
116
116
* <p/>
117
117
* Of special note to authentication module implementors is what modules are allowed in the chain used by a radius
118
-
* client. If an authentication module uses {@link javax.servlet.http.HttpServletRequest} or
118
+
* client. If an authentication module uses {@link jakarta.servlet.http.HttpServletRequest} or
119
119
* {@link javax.servlet.http.HttpServletResponse} they generally won't work for radius clients without modification. For
120
-
* non-http clients the {@link javax.servlet.http.HttpServletRequest} and {@link javax.servlet.http.HttpServletResponse}
120
+
* non-http clients the {@link jakarta.servlet.http.HttpServletRequest} and {@link jakarta.servlet.http.HttpServletResponse}
121
121
* objects will be null typically leading to a {@link java.lang.NullPointerException}. Looking for a value of null is
122
122
* how such modules can tell if they are dealing with a non-http client and adjust their behavior accordingly.
0 commit comments