Bug 1401629 - [RFE] Allow step up authentication with openssh
Summary: [RFE] Allow step up authentication with openssh
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssh
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1195696 1292363 1308421 1401624 1553400
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 18:19 UTC by Dmitri Pal
Modified: 2019-02-11 15:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-11 15:39:19 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dmitri Pal 2016-12-05 18:19:38 UTC
User story:  Step up authentication
- I am a user in IdM
- I am logged in system joined to IdM
- I have a Kerberos ticket that I acquired via a password authentication. It does not have 2FA OTP indicator.
- I access a Linux system joined to IdM using SSH with configured GSSAPI
- Target system requires 2FA for all users (see BZ as a prerequisite)
- IdM is used to store OTP token for me
- I have a token issued for me

My expected user experience: I connect to the system, system prompts me just for my token code (not for my password, this should be very clear). I provide my token code and get logged in. After that I should be able to jump from this box to other Linux systems in the same IdM realm without reauthentication (whether they require 2FA or not). My jumping should only be limited by HBAC.

Bonus: If I forget and instead of just token code provided password together with code would be nice if system would recognize that somehow and still let me in.

There should be a way to configure whether the system allows step-up authentication or not.

Comment 3 Simo Sorce 2019-02-11 15:39:19 UTC
This issue was not selected to be included either in Red Hat Enterprise Linux 7.7 because it is seen either as low or moderate impact to a small amount of use-cases. The next release will be in Maintenance Support 1 Phase, which means that qualified Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released as they become available. We will now close this issue, but if you believe that it qualifies for the Maintenance Support 1 Phase, please re-open; otherwise we recommend moving the request to Red Hat Enterprise Linux 8 if applicable.


Note You need to log in before you can comment on or make changes to this bug.