Asset is accessible by INVALID version in the asset URL
In iRAM AHE Production, The Approved asset "DB2 Best Practices for Security Deployments" is accessible using different versions in the Asset URL. But the version is not at all valid one.
The 1.5.2 version appears for this asset in the database and the Asset Details shows only 1.5.2 in the versions section.
But the same asset is accessible by using 1.1 versions also in the asset URL.
https://w3-03.ibm.com/tools/cm/iram/assetDetail/generalDetails.faces?guid={28373486-9C71-EF69-0521-A9CABE310847}&v=1.5.2
https://w3-03.ibm.com/tools/cm/iram/assetDetail/generalDetails.faces?guid={28373486-9C71-EF69-0521-A9CABE310847}&v=1.1
Kindly, Can you elaborate, what are all the reasons can be cause of this asset is accessible using different versions which is not valid in the Asset URL?
The 1.5.2 version appears for this asset in the database and the Asset Details shows only 1.5.2 in the versions section.
But the same asset is accessible by using 1.1 versions also in the asset URL.
https://w3-03.ibm.com/tools/cm/iram/assetDetail/generalDetails.faces?guid={28373486-9C71-EF69-0521-A9CABE310847}&v=1.5.2
https://w3-03.ibm.com/tools/cm/iram/assetDetail/generalDetails.faces?guid={28373486-9C71-EF69-0521-A9CABE310847}&v=1.1
Kindly, Can you elaborate, what are all the reasons can be cause of this asset is accessible using different versions which is not valid in the Asset URL?
One answer
When you updated an asset while it was version 1.1, and changed it to 1.5.2, you were asked if you want to create a new asset or just update the existing one.
If you had chosen to create a new version, RAM would have create two separated assets ... the original one 1.1, and an updated one 1.5.2 (both having the same GUID). Each one of the assets has its own URL (guid/version).
You have chosen to NOT create a new asset. What RAM did in this case is update the existing 1.1 asset to 1.5.2 .... but now, ... so the old 1.1 asset is now 1.5.2 ... and hence old 1.1 URLs requests will be routed to 1.5.2 ...
The reason for this, is that if one had a bookmark to the old (1.1) asset, this asset is not there anymore... and was updated (replaced) with the 1.5.2 .... both URLs will point to the same asset.
If you had chosen to create a new version, RAM would have create two separated assets ... the original one 1.1, and an updated one 1.5.2 (both having the same GUID). Each one of the assets has its own URL (guid/version).
You have chosen to NOT create a new asset. What RAM did in this case is update the existing 1.1 asset to 1.5.2 .... but now, ... so the old 1.1 asset is now 1.5.2 ... and hence old 1.1 URLs requests will be routed to 1.5.2 ...
The reason for this, is that if one had a bookmark to the old (1.1) asset, this asset is not there anymore... and was updated (replaced) with the 1.5.2 .... both URLs will point to the same asset.