cancel
Showing results for 
Search instead for 
Did you mean: 

How does the url_x number in the url address gets generated?

spanudiez_
Occasional Contributor

How does the url_x number in the url address gets generated?

Hello,

 

How does the url_x number in dana-na/auth/url_x/welcome.cgi gets generated when you have multiple SM clusters? I was under the impression that url_1 stands for the 1st sign-in policy after the default, url_2 for the 2nd and so on, however I now see that the numbers are different between clusters (url_5 is equivalent to url_7 sometimes).

 

Is the incremented depending on the appliance number in the cluster?

 

I couldn't find any info on this on the Internet, if anyone can answer I would be grateful.

 

Thanks,

Diez

3 REPLIES 3
dcvers_
Regular Contributor

Re: How does the url_x number in the url address gets generated?

I don't believe there is any direct relationship between the URL number and the sign-in policy position I think it's more to do with the order the policies were created. And I guess the box may re-used numbers if a policies is deleted.

I do know from experience that the number can change when you do an upgrade/config copy between boxes which can be annoying if users have bookmarked the sign-in page.

 

-red-_
Frequent Contributor

Re: How does the url_x number in the url address gets generated?

From what we have seen, it is a dynamically generated number when the sign-in policy is created. We also had a fair deal of trouble migrating between appliances.. etc. Dealing with users bookmarking the whole URL, including url_xxx can be a nightmare. Thankfully, Exporting/Importing user.cfg preserves the policy numbering, so as long as you can import user.cfg to a new appliance, you can keep the numbers the same.

Kita_
Valued Contributor

Re: How does the url_x number in the url address gets generated?

Yes, the above statements are correct.  When the sign-in policy is created on the device, it is assigned a url number and saved in the system cache.  Once this is created, this cannot be changed.  This is the reason if you create the same sign-in policy on each device, you may get two different results depending on the state of the device.  To ensure all devices are the same, the general recommendation is to export the user.cfg and import to all other devices.  This will ensure all data is the same.