Hi,
We have an issue with Publisher users.
We recently installed ARIS Server 10 and ARIS Publisher Server 10 with standard (derby) database. We linked Publisher user management with ARIS Server UMC during the installation. We can confirm this is done correctly because we can see our user groups in the ARIS Publisher Administration. However we can not see the Users. Reorganizing does not help either.
So at this point we are only able to use anonymously accessed Publisher exports. None of our users can log in to Publisher Home page (other than "root" obviously).
Is this related to the use of demo database system or is there something else we are missing?
Thank you.
Please check if you are really able to list all UMC usergroups in Publisher Administration. You should be able to map UMC usergroups to your exported Publisher usergroups. If it does not work, then your integration with UMC is not configured correctly.
Other problem could be, that your users do not have valid viewer license privilege assigned in UMC. You should see a message about that when you try to log in.. Anyway, it would be interesting to see what kind of error message you are getting while trying to log in..
You should also get more insight by investigation of logs. In this case especially \server\bin\work\work_businesspublisher\base\webapps\businesspublisher\log\externalSystems\ldap.log could give you more hints, or also other logs located in businesspublisher\log folder.
Hi Peter thanks for the comment.
Checked and I can confirm we are able to list all UMC usergroups in Publisher Administration. As a small organization we only have 4 groups and all are listed there.
Licenses also seem to be correct because designer and architect licenses work fine and viewer licenses are assigned just the same way.
The error message is: "Login failed. Please re-enter your username and password." (translated from Turkish)
The logs you pointed out might be really helpful.
---
IT_15c151d2302_SEVERE 2017-05-17T09:34:10,50 com.idsscheer.aris.businesspublisher.application.business.components.login.UMCLogin.ABPUmcAccess.authenticateUser
Authentication failed: null
IT_15c151d2302_SEVERE 2017-05-17T09:34:10,50 com.idsscheer.aris.businesspublisher.application.business.components.login.UMCLogin.ABPUmcLoginContext.authenticateUser
UMC login failed! Token is NULL, probably incompatible UMC libraries or JDK version!
IT_15c151e9faf_SEVERE 2017-05-17T09:35:47,503 com.idsscheer.aris.businesspublisher.application.business.components.login.UMCLogin.IUMCExternalSystemHandlerImpl.getAllUsers
getAllUsers() : null
IT_15c151e9faf_SEVERE 2017-05-17T09:35:47,503 com.idsscheer.aris.businesspublisher.application.business.components.login.UMCLogin.IUMCExternalSystemHandlerImpl.getAllGroups
getAllGroups() : null
IT_15c1acaecca_SEVERE 2017-05-18T12:02:05,514 com.idsscheer.aris.businesspublisher.application.business.components.login.UMCLogin.ABPUmcAccess.authenticateUser
Authentication failed: null
IT_15c1acaecca_SEVERE 2017-05-18T12:02:05,514 com.idsscheer.aris.businesspublisher.application.business.components.login.UMCLogin.ABPUmcLoginContext.authenticateUser
UMC login failed! Token is NULL, probably incompatible UMC libraries or JDK version!
---
Java version seems to be fine but don't really know much about UMC libraries.
Hi Umut,
could you please check if both products are in the same version? I mean if UMC and Publisher are installed in the same version - 10 in your case.. Please check also in the following file \server\bin\work\work_businesspublisher\base\webapps\businesspublisher\config\umcconfig.cfg if it points to correct UMC URL.. maybe by mistake it points still to server with older UMC version? If this is correct, then logs at UMC server should be investigated to find any trace why attempts from Publisher authentication are failing...
HTH
Hi Peter,
The products are definitely installed in the same version. Checked it to be sure.
The URL in the .cfg file is correct. It is in the <IP/umc> format.
I have one last question if it is not too much. We have both designer and publisher in standard database but designer is installed in size <m> and publisher in size <s>. Because version 10 does not let install standard database in <m> size. Can this be the cause of the problem?
Hi Umut,
sizing of both products should not play a role in this problem. Normally such problem occurs when incompatible versions are trying to communicate together, or there is some other unpredictable problem e.g. on UMC side. I would suggest to proceed with UMC logs inspection.. I suppose that there are already some exports taken to Publisher? Because if there is not yet any export, also the authentication will be a problem, because the tenant ID is not yet known for Publisher.. so maybe it is also the thing that should be checked..
HTH
Yes, there are exports published. And now I understand that those exports are the reason why we can see user groups perfectly. Authorized user groups are also taken to publisher when an export is published.
We will continue with the logs and I'll post the solution here when/if we reach it.
Thanks a lot Peter.
Hi Umut,
please notice that the usergroups you see directly in Publisher administration are only exported, as you already mentioned. But then there is a small icon - button in the last column which is used to assign external usergroups/users.. if you click the icon, you should see a dialog, where you can map UMC usergroups to exported usergroups.. If you are able to see the list of all UMC usergroups in the assignment dialog then your integration with UMC is working fine, if not, then you have a general problem, most probably with configuration.. Maybe you will see additional logs in ldap.log when you try to open the assignment dialog..
HTH