The url you started with is the repo that we push to, the support-only repo - this has to do with how artifactory manages permissions:
Instead, please use this one: this aggregates all commercial releases, support or otherwise. This is the url that is referred to in both Edmund's post and mine above:
On the technical side, we're using the concept of a 'virtual' repo that groups all other repos accessible by support users. This way, if we want to add another repo later on, all we do is create it, upload artifacts, and group it into support-commercial-release, and you'll automatically have access to it.
Using the artifactory site is useful to see what objects are in what real repos, but little else. When feeding information to your pom, please use the ones we've posted. Here's the full list of important repo urls, with and without support, gpl and commercial, snapshot and release (and please again note that if you aren't authenticated, the support- repos will be missing artifacts through the web interfaces):
Standard GPL release artifacts:
Standard commercial release artifacts:
Support GPL release artifacts:
Support Commercial release artifacts:
Support GPL snapshot artifacts:
Support Commercial snapshot artifacts:
If your organization uses the Commercial release, and has a support contract, then you only want support-commercial-release, or support-commercial-snapshot, depending on if you want the latest release, or last night's build. If you only want all release artifacts, you only need support-commercial-release, it will contain all artifacts your credentials have access to.