After a server replication, I can no longer generate a personal access token.

Issue Symptoms

 

After a server replication, it is no longer possible to generate a Personal access token.

An error is displayed: "Invalid redirect: https://URL_OF_THE_SERVER does not match one of the registered values: [https://URL_OF_THE_REPLICATED_SERVEUR]

 

Solution

 

  1. From the Administration of iObeya, go to SETTINGS/API.
  2. Then display the "Personal Access Token" configuration.
  3. Finally, adapt the URI with the address of the new server and validate.

Example:

The URL of the new server is: https://serverA.com/

The corresponding URI will be: https://serverA.com/token/managetoken.action?action=generated

 

Support


If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

Administration

After a server replication, I can no longer generate a personal access token.

Issue Symptoms
If you import too many rooms, a timeout will occur.

In your log file app.log, you will have this error:

Caused by: java.lang.OutOfMemoryError: Java heap space

Workaround
First workaround: try to import the rooms gradually

Second workaround: increase the memory allowed to the Java Virtual Machine

Administration

After a server replication, I can no longer generate a personal access token.

Issue Symptoms
The limits do not seem to have changed since the license update.

If you have changed your license, you may encounter limits issues when it is updated .

For example:

If your old license allowed you to create 10 boards maximum per room, the users will not be able to add more than 10 boards after the update. Indeed, the limits of the rooms and the domains are not updated so they are still limited to a maximum of 10.

 

Solution
An administrator must change the limits of the domains and all the rooms accordingly to the new limits of the license.

Go on the administration. Click on "Domains". Click on of the concerned domain. Change the limits & Save.

Now, do the same in the room:

Click on "Domains". Click on the concerned domain. In the list of rooms, click on “Edit information” of the selected room. Change the maximum boards and Save.

 

Support
If you require assistance to resolve the problem, please ask for support. (See Requesting Support)

Administration

After a server replication, I can no longer generate a personal access token.

Issue Symptoms:
When trying to define a permission on a user in the Administration, the action is not saved: the tick is automatically removed.

This behaviour happens in some cases, for instance after removing a user to create the same user but in upper/lowercase.

Workaround:
Log in to your database with the iobeya user.

Then, display the table acl_sid using this request : select * from acl_sid;

Search for the user, you should find the username but in uppercase where the username is in lowercase (or the opposite)

Change the case to the corresponding one, example : update acl_sid set sid="bvarisellaz" where sid="BVARISELLAZ";

Go back to the Administration, and check if it has solved the issue.

Administration

After a server replication, I can no longer generate a personal access token.

Issue Symptoms:
After upgrading iObeya running on an Oracle database, the Email templates in French are not well formatted because of the accented characters.

Solution:
This involves setting the environment variable NLS_LANG=FRENCH_FRANCE.UTF8 on the Windows operating system.

Where to set the NLS_LANG


This setting will be used for ALL Oracle homes.

Right-click the 'My Computer icon -> 'Properties' Select the 'Advanced Tab -> Click on 'Environment Variables' The 'User Variables list contains the settings for the specific OS user currently logged on and the 'System variables system-wide variables for all users. Create the system environment variable NLS_LANG and set its value to : FRENCH_FRANCE.UTF8

To have more details about this procedure, see the original page on http://www.oracle.com/technetwork/products/globalization/nls-lang-099431.html#_Toc110410543

Once this procedure is done, execute the following scripts.

Download refill-after-nlslang-issue.sql Open a terminal window. Go into the directory which contains the script. Execute sqlplus with the IOBEYA user, on the prompt type the IOBEYA password of the database. On the sqlplus prompt, execute the refill-after-nlslang-issue.sql script using the @ followed by the complete path to the script file.

Administration