Deprecated API
Contents
-
Deprecated FieldsFieldDescription
-
Deprecated MethodsMethodDescriptionuse
SamlResponse.getResponseIssuer()and/orSamlResponse.getAssertionIssuer(); the contract of this method is quite controversialuseLogoutResponse(Saml2Settings, LogoutResponseParams)instead, in which case this method becomes completely useless; indeed, invoking this method in an outgoing logout response scenario will cause the response parameters specified at construction time (inResponseToandresponseStatus) to be overwritten, as well as its generated id and issue instant; on the other hand invoking this method in a received logout response scenario does not make sense at all (and in that caseLogoutResponse(Saml2Settings, HttpRequest)should be used instead)useLogoutResponse(Saml2Settings, LogoutResponseParams)instead, in which case this method becomes completely useless; indeed, invoking this method in an outgoing logout response scenario will cause the response parameters specified at construction time (inResponseToandresponseStatus) to be overwritten, as well as its generated id and issue instant; on the other hand invoking this method in a received logout response scenario does not make sense at all (and in that caseLogoutResponse(Saml2Settings, HttpRequest)should be used instead)useLogoutResponse(Saml2Settings, LogoutResponseParams)instead, in which case this method becomes completely useless; indeed, invoking this method in an outgoing logout response scenario will cause the response parameters specified at construction time (inResponseToandresponseStatus) to be overwritten, as well as its generated id and issue instant; on the other hand invoking this method in a received logout response scenario does not make sense at all (and in that caseLogoutResponse(Saml2Settings, HttpRequest)should be used instead)useLogoutResponse(Saml2Settings, LogoutResponseParams)instead, in which case this method becomes completely useless; indeed, invoking this method in an outgoing logout response scenario will cause the response parameters specified at construction time (inResponseToandresponseStatus) to be overwritten, as well as its generated id and issue instant; on the other hand invoking this method in a received logout response scenario does not make sense at all (and in that caseLogoutResponse(Saml2Settings, HttpRequest)should be used instead)this returns just the first e-mail address inContact.getEmailAddresses()
-
Deprecated ConstructorsConstructorDescriptionNot providing a queryString can cause HTTP Redirect binding to fail.Not providing a queryString can cause HTTP Redirect binding to fail.use
LogoutRequest(Saml2Settings, HttpRequest)to build a received request from the HTTP request, orLogoutRequest(Saml2Settings, LogoutRequestParams)withLogoutRequestParams(String, String)to build a new request to be sentuseLogoutRequest(Saml2Settings, HttpRequest)to build a received request from the HTTP request, orLogoutRequest(Saml2Settings, LogoutRequestParams)withLogoutRequestParams(String, String, String)to build a new request to be sentuseLogoutRequest(Saml2Settings, HttpRequest)to build a received request from the HTTP request, orLogoutRequest(Saml2Settings, LogoutRequestParams)withLogoutRequestParams(String, String, String, String)to build a new request to be sentuseLogoutRequest(Saml2Settings, HttpRequest)to build a received request from the HTTP request, orLogoutRequest(Saml2Settings, LogoutRequestParams)withLogoutRequestParams(String, String, String, String, String)to build a new request to be sent