-
Bug
-
Resolution: Done
-
Highest
-
None
-
Frankfurt Release
-
None
In our current environment, only demo and cs0008 can be used to log in to the portal.
If other users such as op0001 are used to log in to the portal, an error will occur and the login will fail.
There are two files (SharedContext.class, SharedContextServiceImpl.class) in /usr/local/tomcat/webapps/ONAPPORTAL/WEB-INF/lib/portal-be-common-3.2.0-classes.jar.
public void addSharedContext(String contextId, String key, String value)
@NotNull
private Date create_time;
When a user (e.g. op0001) logs in, context will be used,
logļ¼
2021-02-03T06:25:09.396Z|d77405ef-c441-4e4b-9ae2-4fb7e5f4e424|https-openssl-nio-8443-exec-47|org.onap.portalapp.portal.service.SharedContextServiceImpl| EPEELFLoggerAdvice#before: entering addSharedContext 2021-02-03T06:25:09.398Z|d77405ef-c441-4e4b-9ae2-4fb7e5f4e424|https-openssl-nio-8443-exec-47|org.onap.portalapp.portal.service.SharedContextServiceImpl| EPEELFLoggerAdvice#after: finished addSharedContext
But when the context is generated, because create_time is not specified, this parameter is null, and the following error is reported.
List of constraint violations:[
ConstraintViolationImpl{interpolatedMessage='may not be null', propertyPath=create_time, rootBeanClass=class org.onap.portalapp.portal.domain.SharedContext, messageTemplate='
'}
However, from the debug log, after the above log reports an error, the login operation still continues. It should be that after the above error was thrown, it was handled in the middle without exiting directly.The impact of this error on login failure has not been confirmed.