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

DDCCGW-651 -Enhance Documentation in praticipant template repo - smart-trust_README_NEW.md #49

Closed
wants to merge 2 commits into from

Conversation

arajnor99
Copy link
Collaborator

Hi @ascheibal @tence

The below points has been covered as part of documentation enhancement with reference to JIRA Ticket # DDCCGW-651
https://jira.telekom.de/browse/DDCCGW-651

Describe how to test the gateway connection (TLS Whitlisting happened, clientcert is working)
Create ( Generate DSC request )
Upload DSCs ( CMS Package Upload as part DSC )
Describe the Certificate renewal process
This need to reviewed by Andreas or Carl

Apart from this approached to use certificate generation and DSC Gen, Upload scripts for Production Environment.
For production recommended to use certificates signed by Trusted Certificate Authority(CA) and added walkthrough steps for Steps to Obtain and Use a CA-Signed Certificate

Copy link
Collaborator

@ascheibal ascheibal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

have a look on my rephrasing, does it meet your intention?

README_NEW.md Outdated
```
openssl x509 -req -in DSC01csr.pem -CA CAcert.pem -CAkey CAprivkey.key -CAcreateserial -days 730 -extensions ext -extfile DSC.conf -out DSCcert.pem
```
**Important Recommendations for Prod**: Please replace your CAcert.pem and CAprivkey.key which issued by your public Trusted Certificate Authority (CA) insterad of self-signged one.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please replace CAcert.pem and CAprivkey.key with signing material from an officially Trusted Certification Authority instead using your own self-signed one.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Andreas for suggestion. I have done correction in my branch "readme_new_enhancement "

**Important Recommendations for Prod**: Please replace CAcert.pem and CAprivkey.key with signing material from an officially Trusted Certification Authority instead using your own self-signed one.

I kindly request to review and approve the same .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants