srinivas

When i open the URL in the browser, it is redirecting to JOSSO login page and on successful authentication, it is redirecting back to the original partner App. But when i open the same URL from a MS Word or MS Excel, it is not redirecting to the partner App, it is loosing the context and opening a page (http://localhost:8080)

I have implemented ForgotAction, i have overriden checkSecurityToken method. Sometimes the session is getting lost when i invoke my overriden method of ForgotAction. If the session is lost, am unable to compare the token which is available in the session. Before invoking , checkSecurityToken the token is available in the session, but after invoking the method, it goes to my overriden method, but inside the method, i dont have the security_token inside the session. This is not happening always, very...

I had an empty value below, after giving host and port, it was resolved <protocol:ws-service-locator endpoint="localhost:8080"/>

The problem is here inside the logs, Host is empty and hence tomocat-coyote is rejecting all the requests 2018-07-13 02:52:53.303 | DEBUG | http-bio-8080-exec-17 | org.apache.axis.transport.http.HTTPSender 519 | writeToSocket | POST ////josso/services/SSOIdentityProviderSoap HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 462 Please...

The problem is here inside the logs, Host is empty and hence tomocat-coyote is rejecting all the requests 2018-07-13 02:52:53.303 | DEBUG | http-bio-8080-exec-17 | org.apache.axis.transport.http.HTTPSender 519 | writeToSocket | POST ////josso/services/SSOIdentityProviderSoap HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 462 Please...

The problem happend because , Tomcat made Strict Validations for the host from 7.0.87 version onwards. Coyote add Enable strict validation of the provided host name and port for all connectors. Requests with invalid host names and/or ports will be rejected with a 400 response. (markt) fix Implement the requirements of RFC 7230 (and RFC 2616) that HTTP/1.1 requests must include a Host header and any request that does not must be rejected with a 400 response. (markt) fix Implement the requirements...

I have attached the log file