Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCM Website Root Address is Not Updated to Have HTTPS #280

Open
6 tasks done
ryanrichter94 opened this issue Oct 30, 2024 · 0 comments
Open
6 tasks done

CCM Website Root Address is Not Updated to Have HTTPS #280

ryanrichter94 opened this issue Oct 30, 2024 · 0 comments
Labels
Bug Tickets that represent defects/bugs. ChocolateyForBusinessAzure Issue affects Chocolatey For Business in Azure Environment. Note the issue will be synced there.

Comments

@ryanrichter94
Copy link
Member

ryanrichter94 commented Oct 30, 2024

Checklist

  • I confirm there are no unresolved issues reported on the Chocolatey Status page.
  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my problem.
  • I have verified this is not an issue for a specific package.
  • I have verified this issue is not security related.
  • I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

In a CCM instance setup using the QSG, we do not set the website address in the CCM interface to have HTTPS. This causes email password reset links and URLs in CCM emails to be unresolvable.

Picture of setting needing change in CCM website.
Image

What is Expected?

We should be updating this value in CM when the Set-SSLSecurity script is run.

How Did You Get This To Happen?

  1. Install QSG on a VM using any of the available SSL options for SSL Setup.
  2. Log in to the CCM website and check the website root address setting.

System Details

  • Operating System: 10.0.20348.0
  • Windows PowerShell version: 5.1.20348.2760
  • Chocolatey CLI Version: 2.3.0
  • Chocolatey Licensed Extension version: 6.2.1
  • Chocolatey License type: Business
  • Terminal/Emulator: Windows PowerShell

Installed Packages

adobereader 2024.3.20112
chocolatey 2.3.0
chocolatey.extension 6.2.1
chocolatey-agent 2.1.3
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
chocolatey-dotnetfx.extension 1.0.1
chocolateygui 2.1.1
chocolateygui.extension 2.0.0
chocolatey-license 2024.12.25.100
chocolatey-management-database 0.13.0
chocolatey-management-service 0.13.0
chocolatey-management-web 0.13.0
chocolatey-windowsupdate.extension 1.0.5
dotnet-8.0-aspnetruntime 8.0.8
dotnet-8.0-runtime 8.0.8
dotnet-aspnetcoremodule-v2 18.0.24201
dotnetfx 4.8.0.20220524
jenkins 2.462.3
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
nexus-repository 3.71.0.6
Pester 5.6.1
sql-server-express 2022.16.0.1000
Temurin21jre 21.0.4.7
vcredist140 14.40.33816

Output Log

N/A

Additional Context

┆Issue is synchronized with this Github issue by Unito

@ryanrichter94 ryanrichter94 added Bug Tickets that represent defects/bugs. ChocolateyForBusinessAzure Issue affects Chocolatey For Business in Azure Environment. Note the issue will be synced there. labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Tickets that represent defects/bugs. ChocolateyForBusinessAzure Issue affects Chocolatey For Business in Azure Environment. Note the issue will be synced there.
Projects
None yet
Development

No branches or pull requests

1 participant