Correct process for requesting and configuring access to Broadcom's private SDK repository within our organization's infrastructure.

Products

• DX SaaS

Issue/Introduction

Working with the Android AXA SDK integrated into the mobile application.

Current Situation: - Previously, we accessed SDK downloads through a remote artifactory connection linked to Broadcom's public repository - Beginning with version 26.X.X, Broadcom has transitioned to a private repository requiring API token authentication - Broadcom has provided documentation on accessing the private repository using API tokens.
Broadcom doc: https://knowledge.broadcom.com/external/article/421110

Challenge: - We contacted the Artifactory team to set up a remote connection to the new private repository - The Artifactory team indicated they do not maintain a shared Broadcom account for SDK downloads.
We need guidance on the proper process for requesting and configuring access to Broadcom's private SDK repository within our organization's infrastructure.

Here is the clarification:

I can access the Broadcom private Artifactory using my personal account's API Key, but I'd prefer not to use it for the remote repository setup in company Artifactory.

The ideal solution would be a shared/service account created for our application or a common token that the APM team owns.

If that's not feasible, I need confirmation that using my personal account's access token for this setup is acceptable.

 

Resolution

The process of generating registry tokens is described here: https://knowledge.broadcom.com/external/article/421110

As I understand it, the customer is expected to use  so called "Enterprise User profile", which is a normal Broadcom support account enabled to use Enterprise Site ID (see https://knowledge.broadcom.com/external/article/142873 --Using your Broadcom Site ID(s) for full support portal access

for details.)

In my opinion, nothing prevents customers to create an additional (generic) Broadcom support account, promote it to Enterprise User profile and generate registry tokens under it.