/build/static/layout/Breadcrumb_cap_w.png

Need to edit the $ticket_url

Since the upgrade to 12.1.168 we are no longer able to use the https://domain/Userui nor the https://domain/Adminui to access SMA.  Our $ticket_url is defaulting to the https://domain/Userui/ticket?ID=##### and we need to update it to go to the https://domain/User/ticket?ID=#####  Not sure how to make that change.  We know we could go into the automatic replies and take out the $ticket_url and manually point it, but we'd like to change it at the source.

We currently do have a ticket with Quest regarding the issues with access, just having some firewall issues with port 22 for the Tether connection.  We're sure once we get our tether connection set up and Quest pushes it's fix, it should also fix the issue with not being able to use the UserUI and AdminUI, but until then, we need to change the link now.

Any suggestions would be appreciated, thank you!


0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
Posted by: Nico_K 1 month ago
Red Belt
0

if you cannot access the appliance then the ticket is the right way. (and if you cannot access how would you change this setting if there were a possibility)

Posted by: Hobbsy 1 month ago
Red Belt
0

The userui and adminui uses in a url are purely so that you can see the full url as opposed to just the admin and user url’s which hide the detail.

Wherever you were using the $ticket_url in the ticket rule or code, why not just change it to type the url, for example

https://domain/User/ticket?ID=

And then add the $ticket_id link, so

https://domain/User/ticket?ID=$ticket_id

that should work

Posted by: barchetta 1 month ago
Black Belt
0

"We're sure once we get our tether connection set up and Quest pushes it's fix, it should also fix the issue with not being able to use the UserUI and AdminUI, but until then, we need to change the link now." 


What fix?  Is this a known issue? 


Comments:
  • Good Morning, We updated to 12.1.168, when that happen, the users were no longer able to access the website using the AdminUI nor UserUI. It also caused a white screen after they logged into either Admin or User, after a refresh of the website, they were able to get in. A work around was to turn off the Acceptable Use Policy, however, we couldn't turn ours off due to Security issues.

    We were able to get our Tether set up with Quest and they pushed a fix to the machine, which has resolved all the issues. Just had to clear out everything from the web browsers. - becca7391 1 month ago
Posted by: becca7391 1 month ago
Senior White Belt
0

Top Answer

We were able to get our Tether set up with Quest and they pushed a fix to the machine, which has resolved all the issues.  Just had to clear out everything from the web browsers.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ