Not clear what this means - you referred to a forums thread that was not posted by us and this does not constitute a recommendation.
If you got a recommendation in some other way, perhaps there was a misunderstanding where we recommended using the approach for a quick test, to be replaced later.
We never recommend using unsupported, undocumented APIs.
Announcement
Collapse
No announcement yet.
X
-
Yes, what is clear to me is that we will need to get support... but you must know that this implementation was also recommended by your support team few years ago. Now we will have to change the whole authetication logic because of a difference between release 12 and 121p, when this clases are still in this release, but we have no more support for this...
Thank you for your help anyway
Leave a comment:
-
Yes, we know. And this class is not documented and not supported, so, you should not be using it, and we will not be providing assistance with using it.
If you need help getting out of this situation, you can get hourly help from our consultants, to
migrate to a supported approach. But this is not a valid support question, because this is an undocumented, unsupported class.
Hope this is now clear.
Leave a comment:
-
Thank you for your response.
RedClieAuthenticator is just an extension of ISC com.isomorphic.auth.Authenticator. The problem seems to be that com.isomorphic.auth.AuthenticationFilter, declared on web.xml is not allowing to call the Overrided "authenticate" method of the first class. In the previous version it was working like a charm but now it seems that an URL must be configured for the autheticator, as the Exception says and we don't know how to configure that. Maybe on ther server.properties we have to add some other key?
Leave a comment:
-
This is not a documented or supported class. We would recommend switching over to whatever WebLogic provides, or any open source Authentication system.
Integrating any such system with SmartClient’s Declarative Security features is very simple, sometimes completely automatic: see the QuickStart Guide.
Leave a comment:
-
Authentication error when implementing tha latest 121p ISC release
Hi Isomorphic,
We have upgrade our framework version frm the 12 to 121p and when autenticating the following error appears on the Tomcat console:
=== 2021-08-25 12:34:48,843 [ec-3] WARN RequestContext - rpcRequest.execute() failed:
java.lang.Exception: No Authenticator configured for this URL
at com.isomorphic.auth.Authentication.clearAuthInfo(Authentication.java:118)
at com.redur.login.rpc.SecureAppDMI.limpiarInicio(SecureAppDMI.java:960)
We have an Authenticator class defined in the server.properties:
authenticator.authRedClie: com.redur.login.rpc.RedClieAuthenticator
authenticator.authRedClie.datasource: userPortalProv
authenticator.authRedClie.usernameField: USUARIO
authenticator.authRedClie.passwordField: PWD
authenticator.authRedClie.cookieDomain: redcliesc.redur.es
authenticator.authRedClie.sessionTimeout: 1800
The authentication declared on the web.xml looks like:
<filter>
<filter-name>AuthenticationFilter</filter-name>
<filter-class>com.isomorphic.auth.AuthenticationFilter</filter-class>
<init-param>
<param-name>authenticator</param-name>
<param-value>authRedClie</param-value>
</init-param>
<init-param>
<param-name>maxTries</param-name>
<param-value>-1</param-value>
</init-param>
<init-param>
<param-name>defaultLoginRedirect</param-name>
<param-value>/secureApp/index.jsp</param-value>
</init-param>
<init-param>
<param-name>loginPage</param-name>
<param-value>/secureApp/login.jsp</param-value>
</init-param>
<init-param>
<param-name>rules</param-name>
<param-value>
ignore:#index.jsp#
ignore:#nonAuthenticatedOperations.jsp#
match:#.*#
</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>AuthenticationFilter</filter-name>
<url-pattern>/PortalProvSc/secureApp/*</url-pattern>
</filter-mapping>
Please let us know what can be missing.
Thank you in advance!Tags: None
Leave a comment: