I’m getting some issues with the people record. Once created, it is not getting associated with the triPeople object, nor the My Profile object. This prevents a new user from logging into the environment. The associated My Profile is also missing even after making the user an active TRIRIGA user. Any reasons for this?
We are looking for an approach to the above issue which will keep the page alive. We have tried alternatives such as explicitly calling a data source. And we are looking at handling session cookies.
The UX app can make sure it does not time out by making a call to a specific end-point. You can make an Ajax call to the following URL, which will update the last access time and keep the session alive:
There may also be an issue where the menu does not load, unless you use the CUILOAD command directly to load the TrgaAcad_en.cuix directly from the install directory. Then, attempting to login results in a _TRGA_LOGIN Unknown command “TRGA_LOGIN” message. The cause of this issue is that the CAD Integrator/Publisher (CI) is not initializing correctly…
Assuming NETLOAD works, the main issue is that probably the CI installer does not have permission to update the registry. CI actually uses the JVM and the command line to update the registry, so on certain secure systems, it may not be allowed to update the registry as needed to tell AutoCAD to load CAD Integrator…
The main issue is a permission issue where the CI installer cannot update the Windows registry to enable automatic loading, which is outside the control of the CI installer. If the CI installer cannot update the registry, then see the workaround…
We are running TRIRIGA 126.96.36.199 platform and TRIRIGA 10.5 application. We have a requirement from our customer, for Sarbanes-Oxley (SOX) compliance reasons, that we need to change the “System” user password in TRIRIGA. We have done this in the past. However, the old option now appears to have become read-only, so we can’t do it the same way. Any ideas how we can update this password now?
Here are some things that might be preventing you from updating the password:
- 1. The logged-in user does not have security access to update the password, or a workflow has triggered on the record that has modified the metadata, and made the password fields or its section non-editable.
- 2. The record is in a state that only supports read-only actions. This makes the record non-editable.
- If you are logged in as Admin and cannot modify the password, I’d confirm that the System user is still part of the Admin group.
- If you are trying to change the System password as another user that is not an Admin, I would put that user in the Admin group temporarily to see if this gets past your issue.
- If you can confirm that a user in the Admin group cannot modify the record, I would look at workflows that are changing the metadata and the record state.
- If you cannot access the account as the System user, you can temporarily clear the System password to blank (null), so that you can login as Admin and reset the password. For example, via an update SQL script:
- update user_credentials set password = null where user_account = ‘system’.
I would like to know if it is possible to use a UX login template, created as a UX view and accessed with the WebViewSync.jar, as the ALTERNATE_INDEX_HTML. Currently, I have this configuration in the TRIRIGAWEB.properties:
- ALTERNATE_UX_LOGIN_VIEW: cstMeetingRoomsManagerViewAutoLogin
I would like to use the same login page in both places, accessing classic TRIRIGA normally, and also accessing a UX application. Can I set something like this?
- ALTERNATE_INDEX_HTML: cst-meeting-rooms-manager-autologin.html
- ALTERNATE_RESOURCE_DIRECTORY: /root/tririga/p/web
Currently, TRIRIGA does not support using a UX login view as the ALTERNATE_INDEX_HTML. That’s because of the dependency from UX views to Polymer libraries and UX components.
[Admin: To see other related posts, use the Alternate tag.]
In the TRIRIGA Admin Console, under “System Manager”, there is an option to “lock” the server so that maintenance can be done. When the server is up and in a “locked” status, users will not be able to log into TRIRIGA, but administrators can. Users will get a message when they attempt to log in that the system is “locked”.
It is important to know that if your agents are all stopped when you put the system in a “lock” status, and you restart your server, the server will not start back up. This is by design, because the server thinks an upgrade is being done, and you do not want to start up your server if an upgrade is in process.
[Admin: This post is related to the 11.28.12 post about disabling user logins to perform system maintenance.]
I have a problem. I have developed a UX app for a client, but it is totally necessary that the session is kept alive. I have tried different ways to do it, but I haven’t had any success. So I came here a little bit desperate, looking for new ideas to try.
- (1) First Solution: Using <triplat-login> into the application. The login control was developed as follows… Normally, the application reconnects automatically and correctly. But sometimes it doesn’t, and it returns to the login webpage or gets stuck. So this solution is not valid.
- (2) Second Solution: Using alternative UX login webpage. The next solution was working with the alternative login webpage for UX applications, because the problem of the first solution was that it sometimes returns to the login webpage… When the application returns to the alternate UX login page, it normally reconnects correctly. But sometimes it doesn’t, and it returns an error into the console…
- (3) Third Solution: Force logout and login again. The third and last solution was a mix of the previous two solutions, but also adding the <triplat-signout-button>… This solution has the same problem as the second solution. Normally, it works. But sometimes it returns an error…
Sorry for the very long text. Any new ideas to try?
Have you tried to increase the HTTP session timeout?