Hi Christian and Alexander,
considering I'm still in the initial phase of the project I customised the
Dockerfile to install the needed package.
For those interested here is the fork with the branch:
https://github.com/rrotondo/freeipa-container/tree/add-ipa-fas
with a custom version for
On Чцв, 04 кра 2024, Riccardo Rotondo via FreeIPA-users wrote:
Hi Alexander,
Thank you Alexander, this solution probably fits our needs.
My only problem now is the I configured freeipa with docker, and in
that image developer didn't include the Fedora Account System plugin
for IPA so in the log
On 04/04/2024 13.24, Riccardo Rotondo via FreeIPA-users wrote:
Hi Alexander,
Thank you Alexander, this solution probably fits our needs.
My only problem now is the I configured freeipa with docker, and in that image
developer didn't include the Fedora Account System plugin for IPA so in the
Hi Alexander,
Thank you Alexander, this solution probably fits our needs.
My only problem now is the I configured freeipa with docker, and in that image
developer didn't include the Fedora Account System plugin for IPA so in the log
I found:
ERROR in middleware: Uncaught IPA exception:
On Пан, 25 сак 2024, Riccardo Rotondo via FreeIPA-users wrote:
Hi,
I'm writing here because, 6 years after, I have the same question cknight
previously asked.
Any update on that?
My users only login to web UI and can't perform ldap search so the only
way they can obtain users info it's from
Hi,
I'm writing here because, 6 years after, I have the same question cknight
previously asked.
Any update on that?
My users only login to web UI and can't perform ldap search so the only way
they can obtain users info it's from the "Users" page
("#/e/user/details/userame")
I understand
On ti, 11 joulu 2018, cdknight via FreeIPA-users wrote:
Thanks for the responses. Therefore, I will instead have to restrict
access to the Web UI either by creating an HBAC rule (this is my
understanding of what to do), and instead allowing them access a
secondary self-service UI like
Thanks for the responses. Therefore, I will instead have to restrict access to
the Web UI either by creating an HBAC rule (this is my understanding of what to
do), and instead allowing them access a secondary self-service UI like
https://github.com/ubccr/mokey. While this secondary software
On ti, 11 joulu 2018, cdknight via FreeIPA-users wrote:
When a user signs in to FreeIPA, I do not want them to be able to view
the list of users in my LDAP server under the "Active users" link. I
still want them to be able to administer self-service, so they can
reset their password, add OTP
On 12/11/18 1:36 AM, cdknight via FreeIPA-users wrote:
When a user signs in to FreeIPA, I do not want them to be able to view the list of users
in my LDAP server under the "Active users" link. I still want them to be able
to administer self-service, so they can reset their password, add OTP
10 matches
Mail list logo
