[SAML Platform Authentication] Configuration login does not work for this plugin
Forge component by Alexandre Costa
Published on 13 Jan 2021

Here is a full log from ServiceCenter:


Error executing query. Error in advanced query GetLifetimeRole in Platform_GetServiceCenterRole in Security in LifetimeIdPClient (SELECT TOP 1 Role.[Name] FROM {User} INNER JOIN OS@Table1 UserRoles ON UserRoles.[UserId] = {User}.[Id] INNER JOIN OS@Table2 Role ON UserRoles.[RoleId] = Role.[Id] WHERE {User}.[Id] = @UserId AND {User}.[Is_Active] = 1 AND Role.[Name] <> 'Everyone'): ORA-00923: FROM keyword not found where expected

eSpaceVer: 2 (Id=39, PubId=64, CompiledWith=10.0.1023.0)
 RequestUrl: https://fastqls-flt.dms.ort.usw2.ficoanalyticcloud.com/LifetimeIdPClient/CommonFlow.Login.jsf (Method: POST)
 ClassLoader: ModuleClassLoader for Module "deployment.LifetimeIdPClient.war:main" from Service Module Loader(1520519490)
 FilePath: /LifetimeIdPClient/CommonFlow.Login

Rank: #88

Hi vamsikrishna,

look like sql query problem.

Are you using SQL query on this page.

this sql query should be {Role}.[Name] 


Rahul Sahu

Hi Rahul,

This is the error we noticed, while accessing lifetimeidp client configuration. 



Rank: #57777

Hi Rahul Sahu,

I am working with Vamsi and we were able to fix the SQL problem. The issue was that the plugin had a wrong SQL query, the format looked like MySQL syntax, once we changed to Oracle it worked fine. 

Now we have another issue on the configuration form, more specifically the second tab called "SP Connector settings and Claims". It never saves the configuration and reset to the default values as follows.

All the other tabs are working fine but this one.  We debugged using the Service Studio and it looks like it is a problem with the Form validation.  For some reason it always returns "false".

We went through all the fields on the form and we are filling all the fields that is mandatory but the validation is always false.  Any ideia what is going on?



Rank: #256

Andre, it would be really helpful if you could post the fix for that query. This way other people don't have to go through the same pain and can easily fix the same problem. Thanks !

Rank: #256

To give a bit more info on this. If you are using Oracle as database, you need to remove the "top 1" from all the queries in order for this component to work. In my opinion, this should be fixed in the component.