<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/pam-configs/radius-optional, branch sever-sever-patch-1</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=sever-sever-patch-1</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=sever-sever-patch-1'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2023-09-19T18:03:51+00:00</updated>
<entry>
<title>pam: T5577: Improved PAM configs for RADIUS and TACACS+</title>
<updated>2023-09-19T18:03:51+00:00</updated>
<author>
<name>zsdc</name>
<email>taras@vyos.io</email>
</author>
<published>2023-09-19T18:03:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=784fb7dc2ccc63789ed85d803e3ae41eef0e0253'/>
<id>urn:sha1:784fb7dc2ccc63789ed85d803e3ae41eef0e0253</id>
<content type='text'>
After sources analysis, we found the next possible return statuses for PAM
modules:

1. pam_tacplus

    Auth:

    - PAM_AUTH_ERR
    - PAM_AUTHINFO_UNAVAIL
    - PAM_AUTHTOK_ERR
    - PAM_BUF_ERR
    - PAM_CRED_INSUFFICIENT
    - PAM_PERM_DENIED
    - PAM_SUCCESS
    - PAM_USER_UNKNOWN

    Account:

    - PAM_AUTH_ERR
    - PAM_AUTHINFO_UNAVAIL
    - PAM_PERM_DENIED
    - PAM_SUCCESS
    - PAM_USER_UNKNOWN

    Session:

    - PAM_AUTHINFO_UNAVAIL
    - PAM_SESSION_ERR
    - PAM_SUCCESS
    - PAM_USER_UNKNOWN

2. pam_radius_auth

    Auth:

    - PAM_ABORT
    - PAM_AUTH_ERR
    - PAM_AUTHINFO_UNAVAIL
    - PAM_AUTHTOK_ERR
    - PAM_BAD_ITEM
    - PAM_BUF_ERR
    - PAM_CONV_AGAIN
    - PAM_CONV_ERR
    - PAM_IGNORE
    - PAM_NO_MODULE_DATA
    - PAM_PERM_DENIED
    - PAM_SUCCESS
    - PAM_SYSTEM_ERR
    - PAM_USER_UNKNOWN

    Account:

    - PAM_SUCCESS

    Session:

    - PAM_ABORT
    - PAM_AUTHINFO_UNAVAIL
    - PAM_BAD_ITEM
    - PAM_BUF_ERR
    - PAM_CONV_AGAIN
    - PAM_CONV_ERR
    - PAM_IGNORE
    - PAM_NO_MODULE_DATA
    - PAM_PERM_DENIED
    - PAM_SUCCESS
    - PAM_SYSTEM_ERR
    - PAM_USER_UNKNOWN

PAM configurations were replaced with tuned versions to take this into account.
</content>
</entry>
<entry>
<title>RADIUS: T5577: Added `mandatory` and `optional` modes for RADIUS</title>
<updated>2023-09-13T17:41:43+00:00</updated>
<author>
<name>zsdc</name>
<email>taras@vyos.io</email>
</author>
<published>2023-09-13T09:41:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=5181ab60bb6d936505967d6667adc12c5ecb9b64'/>
<id>urn:sha1:5181ab60bb6d936505967d6667adc12c5ecb9b64</id>
<content type='text'>
In CLI we can choose authentication logic:

  - `mandatory` - if RADIUS answered with `Access-Reject`, authentication must
  be stopped and access denied immediately.
  - `optional` (default) - if RADIUS answers with `Access-Reject`,
  authentication continues using the next module.

In `mandatory` mode authentication will be stopped only if RADIUS clearly
answered that access should be denied (no user in RADIUS database, wrong
password, etc.). If RADIUS is not available or other errors happen, it will be
skipped and authentication will continue with the next module, like in
`optional` mode.
</content>
</entry>
</feed>
