spring-saml IDPSSODescriptor wasn't found after time - java

I have a system that works, but after certain period of time I have this kind of problem:
2017-08-31 15:31:00 ERROR UT005023: Exception handling request to /spring-security-saml2-sample/saml/login: javax.servlet.ServletException: org.opensaml.saml2.metadata.provider.MetadataProviderException: Metadata for entity ****** and role {urn:oasis:names:tc:SAML:2.0:metadata}IDPSSODescriptor wasn't found
2017-08-31 15:31:02,922 ERROR [io.undertow.request] (default task-29) UT005023: Exception handling request to /spring-security-saml2-sample/: org.apache.jasper.JasperException: java.lang.NullPointerException
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:473)
My "express" solution is to restart wildfly but I'd like to resolve it definitively. What can I do?

I recently ran into this same issue using CachingMetadataManager. In the docs, it says,
Cache is cleaned whenever some of the providers published an observed
message
My current guess is that the IDP either published a message and one of our severs didn't get it, or that the IDP made changes to the metadata without publishing a message. However, simply rebuilding the environment did fix the issue.

Related

spring LDAP does not throw specific error code

Environment
LDAP Server: TurnKey OpenLDAP
Spring-ldap-core version: 2.3.3.RELEASE
What is the activity
User is locked in LDAP server
User attempts to login through our webapp
Login failed
Error code 49 - Invalid Credentials is thrown
What is expected
Specific exception should be thrown(eg: Error code 775 USER_ACCOUNT_LOCKED)
Excepion
Some information like comment and data are not found in the exception
org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:191)```
The LDAP protocol RFC doesn't provide the level of granularity that you want for a rejected authentication request, it's simply error code 49 invalidCredentials. There is no account locked in the standard.
In another LDAP wiki documentation here about error codes, it also specifies that error code 49 is valid for locked accounts.
If you are keen on having this functionality you could opt to take control of your security layer and impose a maximum retry count for your application (rather than relying of whatever is default in a third party LDAP server), keep track if it's reached, and throw/return the appropriate response that you want. I can see an example of how you could do that in this post, but I would invest a bit more time in finding the best solution if you want to go this way.
LDAP specification is base. It defines error codes.
Implementation of LDAP such as OPEN_LDAP, ACTIVE_DIRECTORY etc.. may define its own sub-error codes with exception message. Active Directory supplies its own sub-error codes within the error message.
ldap-related-rfcs
active-directory-error-codes

Unknown Host Exception Yet Website Is Accessible

I'm using IntelliJ IDEA to implement the Spring Guide for consuming REST services
https://spring.io/guides/gs/consuming-rest/
When I run the Application class I receive the following error
Exception in thread "main" org.springframework.web.client.ResourceAccessException:
I/O error on GET request for "https://gturnquist-quoters.cfapps.io/api/random":
gturnquist-quoters.cfapps.io;
nested exception is
java.net.UnknownHostException: gturnquist-quoters.cfapps.io
The URL itself (https://gturnquist-quoters.cfapps.io/api/random) opens fine in a browser and my HTTP Proxy settings in IntelliJ can connect to the site without any issues. Why would an UnknownHostException be thrown here?
Hey I know this is a bit late, but here is what I had to do to resolve this issue. Even if you are using system proxies, for whatever reason, using this type of GET request requires you to build out a proxy to use in the call, like so.
Example Image

java.lang.ExceptionInInitializerError on JSP page

HTTP Status 500 - Internal Server Error
type Exception report
messageInternal Server Error
descriptionThe server encountered an internal error that prevented it from fulfilling this request.
exception
java.lang.ExceptionInInitializerError
note The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 4.0 logs.
GlassFish Server Open Source Edition 4.0
Got When I Run my JSP project on Netbeans 7.3
How to solve this ?
this is because there is a number to long in the code, maybe go back and check if you added a number to long and you just need to change it, check all of the integers!

org.apache.cxf.interceptor.Fault: Marshalling Error: null

I have created a webservice using cxf 3.4.1
When I send a request to the webservice it works fine but sometimes for one
or other request it gives me error with the following stack trace on the
console.
I am using jdk 1.6 , jboss 5.1.0 GA , jbossws-cxf-3.4.1.GA
Can anybody help me resolving this issue?
I receive the following error:
org.apache.cxf.interceptor.Fault: Marshalling Error: null
at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.java:252)
at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:169)
at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writeParts(AbstractOutDatabindingInterceptor.jav:110)
Put the source code alongwith your questions for better responses.
This looks like the client has closed the connection for some reason. Either it timed out or the client ended or similar. Basically, the server is trying to write a response out, but the socket has been closed.
Nirmal is right. That's the typical error of CXF when the client closes the connection early.
But there can be too many causes to get the specific answer just putting the exception message.
I had the same error, and in my case the reason was that I had declared an abstract class of exception in the WS, so when the client tried to unmarshall it, an exception was thrown and client had closed the connection early.
My advice is to put a breakpoint in the cause exception and debug the error.

Logs for debugging a GAE app

I've deployed an application to GAE and now I get "404 NOT_FOUND" error.
Where I can find out the detailed information about this error (stack trace) ?
In "Logs" and "Admin logs" I didn't find anything useful.
Note: By "logs" I do not mean logs for site visiting statistics.
Update: Now I managed to get rid of the 404 error. However, now I get another logging related error:
[s~project-control-center/1.352785038340247795].:
Failed to instantiate [ch.qos.logback.classic.LoggerContext]
How can I fix it?
There have been some problems recently with displaying the logs in the admin console. You can try downloading the logs:
Log Download Docs
Set --severity=0 to get the DEBUG level.
All requests are logged, but the default view is to show only logs with error messages. Click on 'Show: All requests' on the top of the logging page to show all requests.
There's unlikely to be a stacktrace for a 404 not found message, because no error occurred - the URL you attempted to fetch simply didn't exist.

Categories

Resources