YaST-related parts for 389-ds ldap server #545
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- which does no longer exist
- add procedure how to create new DS instance with yast - add preliminary screenshot - add a bunch of question for firstyear - make section about configuring LDAP users and groups with yast a subsection of the new sect1
Firstyear
reviewed
Jan 21, 2020
Firstyear
reviewed
Jan 21, 2020
Firstyear
reviewed
Jan 21, 2020
taroth21
changed the title
- update screenshot with SLE 15 SP2 version - add short explanations by William for each text field
- based on firstyears input - raise more questions
- add more feedback by firstyear: * clarify that PEM/P12 is either 'none or 'both' * adjust p12 string * add remarks with pointers * update screenshot of yast2 ldap-server
- add info provided by firstyear - add this to overview of required steps - move some info from Admin Credentials session to there - ToDo: add pointer from yast subsection
- some minor modifications in YaST section
- rephrase/shorten some sentences - use consistent names in examples and YaST screenshot - add missing option in command - correct some flaws
- profile related links accordingly
- as the related yast module no longer exists -> reducing the chapter to configuration of auth clients
- as discussed with firstyear
taroth21
added a commit
that referenced
this pull request
Jan 29, 2020
from 'master' - affected files: * security_auth.xml * security_ldap.xml * security_ldap_kerberos_ad_yast.xml * yast2_userman.xml * ay_bigfile.xml * security_kerberos.xml * entity-decl.ent * net_slp.xml * security_ad_support.xml * yast2-ldap-server.png (new image) - based on the following PRs: * #545 * #514 * #403
taroth21
added a commit
that referenced
this pull request
Jan 29, 2020
from 'master' - affected files: * security_auth.xml * security_ldap.xml * security_ldap_kerberos_ad_yast.xml * yast2_userman.xml * ay_bigfile.xml * security_kerberos.xml * entity-decl.ent * net_slp.xml * security_ad_support.xml * yast2-ldap-server.png (new image) - based on the following PRs: * #545 * #514 * #403 (cherry picked from commit 2e370b8)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Working with @Firstyear to finish the YaST parts of the 389 ds server documentation.
Checklist
Are backports required?