|
| 1 | +:_mod-docs-content-type: PROCEDURE |
| 2 | + |
| 3 | +[id="adding-an-scc-account-to-{project-context}-by-using-web-ui"] |
| 4 | += Adding an SCC account to {Project} by using {ProjectWebUI} |
| 5 | + |
| 6 | +Add your SCC account to {Project}. |
| 7 | + |
| 8 | +[WARNING] |
| 9 | +==== |
| 10 | +The SCC Manager plugin does not support multiple SCC accounts within one organization. |
| 11 | +Add an additional SCC account only if you want to switch to using another SCC account. |
| 12 | +
|
| 13 | +If you need to use additional SCC accounts, add them to other organizations. |
| 14 | +==== |
| 15 | + |
| 16 | +.Prerequisites |
| 17 | +* You have installed the SCC Manager plugin on your {Project}. |
| 18 | +For more information, see xref:Installing_the_SCC_Manager_plugin_{context}[]. |
| 19 | + |
| 20 | +.Procedure |
| 21 | +. Optional: In the {ProjectWebUI}, navigate to *Content* > *Content Credentials* and click *Create Content Credential*. |
| 22 | ++ |
| 23 | +Add the GPG public key for SLES 15 SP3 from https://www.suse.com/support/security/keys/[suse.com]. |
| 24 | +. In the {ProjectWebUI}, navigate to *Content* > *SUSE Subscriptions*. |
| 25 | +. Click *Add SCC account*. |
| 26 | +. In the *Name* field, enter a name for your SCC account in {Project}. |
| 27 | +. In the *Login* and *Password* fields, enter your SUSE credentials. |
| 28 | +. In the *Base URL* field, you can enter the base URL for the Suse Customer Center. |
| 29 | +By default, it is set to `\https://scc.suse.com`. |
| 30 | +. Click *Test connection* to verify your account information. |
| 31 | +. Optional: Set a *Refresh interval* to periodically update the SCC authentication token. |
| 32 | +Note that this does not refer to synchronizing content to {Project}. |
| 33 | +. Optional: Set a *Refresh time* to specify the time of the refresh of the SCC authentication token. |
| 34 | +. Optional: In the *GPG key for SUSE products* field, you can select the previously created content credential to automatically add a GPG public key to your SUSE products. |
| 35 | +`zypper` automatically verifies the signatures of each software package to ensure their authenticity. |
| 36 | ++ |
| 37 | +[NOTE] |
| 38 | +==== |
| 39 | +You can also set the GPG public key for repositories from SUSE at a later stage. |
| 40 | +However, changing it does not affect already synchronized products. |
| 41 | +If you already have synchronized products in {Project}, navigate to *Content > Products* and replace the GPG key in each respective product. |
| 42 | +==== |
| 43 | +. Optional: From the *Download Policy* list, select a download policy for your SUSE products. |
| 44 | +For more information, see xref:Download_Policies_Overview_{context}[]. |
| 45 | +. Optional: From the *Mirroring Policy* list, select a mirroring policy for your SUSE products. |
| 46 | +For more information, see xref:Mirroring_Policies_Overview_{context}[]. |
| 47 | +. Click *Submit* to save your SCC account to {Project}. |
| 48 | +. In the {ProjectWebUI}, navigate to *Content* > *SUSE Subscriptions*. |
| 49 | +. Select your SCC account and click *Sync* to fetch a list of products associated to your SCC account. |
0 commit comments