This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1765067 - [RFE]Adding rsa keys under 2048 bits or dsa keys in IPA web UI
Summary: [RFE]Adding rsa keys under 2048 bits or dsa keys in IPA web UI
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: ---
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-24 09:49 UTC by Chetan Patil
Modified: 2023-09-18 18:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 18:08:24 UTC
Type: Story
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-6895 0 None None None 2021-09-23 11:26:01 UTC
Red Hat Issue Tracker   RHEL-4840 0 None Migrated None 2023-09-18 18:03:45 UTC

Description Chetan Patil 2019-10-24 09:49:22 UTC 
1. What is the nature and description of the request?

I want to be able to set restrictions on the SSH public keys field for the users.
It should not be possible to upload weak keys.

2. Why do you need this? (List the business requirements here)

This is needed for security purpose.

3. How would you like to achieve this? (List the functional requirements here)

We could set global settings similar to the gitlab configuration, as described here: https://docs.gitlab.com/ee/api/settings.html

* rsa_key_restriction - The minimum allowed bit length of an uploaded RSA key. Default is 0 (no restriction). -1 disables RSA keys.
* dsa_key_restriction - The minimum allowed bit length of an uploaded DSA key. Default is 0 (no restriction). -1 disables DSA keys.
* ecdsa_key_restriction - The minimum allowed curve size (in bits) of an uploaded ECDSA key. Default is 0 (no restriction). -1 disables ECDSA keys.
* ed25519_key_restriction - The minimum allowed curve size (in bits) of an uploaded ED25519 key. Default is 0 (no restriction). -1 disables ED25519 keys.

4. For each functional requirement listed, specify how Red Hat can test to confirm the requirement is successfully implemented with you.

* Set up an IPA server with the WebUI in the VM
* Create a single user
* login in the webui with that username, adding a prohibited key (as per configuration parameters described in point 3.) should result in an error, with no change applied.

5. Do you have any specific time-line dependencies and which release would you like to target (i.e. IPA Version)?

I would like to get this feature on my current set up on RHEL 7 (updated to the latest minor revision), ideally in the version provided in the repository rhel-7-server-rpms. I currently use 4.6.5 but I can upgrade if an upgrade plan is provided. In all cases, the solution should work under RHEL 7.

6. Would you be able to assist in testing this functionality if implemented?

Yes
Comment 7 RHEL Program Management 2023-09-18 18:01:48 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-18 18:08:24 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.