I have a local SMT repository that is snyc'd to the Suse repositories, and then I clone it into an offline environment with local clients pointed at it for updates. I have had no issues doing this with SLES11 hosts, but today I am trying on a SLES12 box and zypper wants to authenticate on SCC to confirm registration. Since this is a production environment and this will never be possible, looking for guidance on how to stop this? IS there a way around it?

sles12-base-01:/etc/zypp/repos.d # zypper lp
Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP2_x86_64'.
Authentication required for 'https://scc.suse.com/access/services/1346?cookies=0&credentials=SUSE_Linux_Enterprise_Server_12_SP2_x86_64'
User Name: SCC_ab3************
Problem retrieving the repository index file for service 'SUSE_Linux_Enterprise_Server_12_SP2_x86_64':
Login failed. (https://scc.suse.com/access/services/1346/repo/repoindex.xml?cookies=0&credentials=SUSE_Linux_Enterprise_Server_12_SP2_x86_64): The requested URL returned error: 401
Check if the URI is valid and accessible.
I am a little confused with why it is trying to hit that repo as it is not one that is defined/enabled.

sles12-base-01:/etc/zypp/repos.d # zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.

# | Alias             | Name              | Enabled | GPG Check | Refresh | URI                                                                        
1 | SLES12sp2-Updates | SLES12sp2-Updates | Yes     | (r ) Yes  | Yes     |
Thx for any help!