Limited access blocked

okajimmy
New Contributor

Hi,

I enabled the limited access by accident to all jamf instance :/

As am newbie in jamf environment, i would like to know if there is any work around to bypass this problem, and to gain access to the web console again.

Regards

1 REPLY 1

ejculpepper
Contributor

Hello @okajimmy ,

I believe this can be reversed by modifying the value located within the "limited_access_mode_settings" in your mySQL database. I would make sure you have a good backup of your database before the change, and would advise to check with your Jamf representative before making changes to your production environments database. Changes made to your database are done at your own risk.

I tested this in my development environment running JSS version 10.9 and InnoDB for the MySQL database engine. I enabled limited access mode, which denied me access to my web console, then went into MySQL command line and ran the following commands:

  • use database name
  • SELECT * FROM limited_access_mode_settings;
  • UPDATE limited_access_mode_settings SET access_mode = '0';

First command is to tell the command line to use the database that your JSS nodes refer too, you will need to replace "database name" with the correct name of your database.

Second command is to view the table you need to make changes too, just to ensure your update statement is correct.

The third command updates the "access_mode" column in the "limited_access_mode_settings" table to 0 for all rows, which effectively removes limited access. You can then run the second command again to ensure the change was made successfully.

Your command might need to be modified a bit, as my development environment is not clustered, it is just a single server. You may have multiple entries in the table that need to be modified to disable limited access on all nodes. Also, if you are not running version 10.9 or InnoDB, the table names may be different as well.

After these changes were made, I restarted the Apache service and was able to access my web console again.

Again, I would advise to check with your Jamf representative before making any changes to the database, and I would make sure a good backup has been taken of the database. You make changes to your database at your own risk, as I have been told by support, which is why I check with them before modifying my production environment.