Morning folks
I am currently working on a little pet project which I think some would
find useful.
I would like to introduce some group policy like functionality into a
FreeIPA domain.
For example:
In an environment running FreeIPA Server with Fedora or RHEL based
workstations, I would like to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/04/2014 10:22 PM, Matt . wrote:
> Hi Guys,
>
> I'm trying to auth Dovecot agains FreeIPA using this tut:
>
>
http://www.freeipa.org/page/Dovecot_IMAPS_Integration_with_FreeIPA_using_Single_Sign_On
>
> (and also Postfix using this:
https://www.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/12/13 19:22, Dmitri Pal wrote:
> On 12/06/2013 08:56 AM, Simo Sorce wrote:
>> Maybe you can open a RFE to let the framework support jpegphoto
>> natively ? Simo.
>
> Yes, that would be really nice.
>
Here you go folks, first trac ticket so be g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/13 22:58, Simo Sorce wrote:
> On Thu, 2013-12-05 at 22:32 +0000, Dale Macartney wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi folks
>>
>> Just a quick mail from me before I call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks
Just a quick mail from me before I call it a night.
Today I've added user display pictures/avatars into FreeIPA, detailed here.
https://www.dalemacartney.com/2013/12/05/adding-display-picturesavatars-red-hat-idmfreeipa/
As well as pulling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/15/2013 10:06 AM, Dale Macartney wrote:
>
>
> On 03/15/2013 10:03 AM, Dale Macartney wrote:
>
>
> > On 03/15/2013 09:52 AM, Sumit Bose wrote:
> > > On Fri, Mar 15, 2013 at 09:38:04AM +, Dale Macartney w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/15/2013 10:03 AM, Dale Macartney wrote:
>
>
> On 03/15/2013 09:52 AM, Sumit Bose wrote:
> > On Fri, Mar 15, 2013 at 09:38:04AM +, Dale Macartney wrote:
> >>
> > Morning all
>
> > I have setup the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/15/2013 09:52 AM, Sumit Bose wrote:
> On Fri, Mar 15, 2013 at 09:38:04AM +0000, Dale Macartney wrote:
>>
> Morning all
>
> I have setup the domain trust set up and have errors when trying to map
> groups from AD to IPA
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
I have setup the domain trust set up and have errors when trying to map
groups from AD to IPA
Environment is IPA 3.0 on RHEL 6.4 and Windows 2012
When adding groups, I get the following.
[root@ds01 ~]# ipa group-add --desc='Active Dire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2013 12:48 PM, Anthony Messina wrote:
> On Wednesday, March 13, 2013 12:41:05 PM Dale Macartney wrote:
>> Silly mistake on my part. Simple perms issue with keytab file.
>>
>> Below is a working config of postfix with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2013 08:11 AM, Dale Macartney wrote:
>
>
> On 03/14/2013 08:07 AM, Martin Kosek wrote:
> > On 03/13/2013 11:02 PM, Natxo Asenjo wrote:
> >> On Wed, Mar 13, 2013 at 10:45 PM, Dale Macartney
> >> wrote:
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2013 08:07 AM, Martin Kosek wrote:
> On 03/13/2013 11:02 PM, Natxo Asenjo wrote:
>> On Wed, Mar 13, 2013 at 10:45 PM, Dale Macartney
>> wrote:
>>> I've just deployed a RHEL 6.4 proxy and the guide is still acc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2013 09:20 PM, Natxo Asenjo wrote:
> hi,
>
> following the howto
>
http://freeipa.org/page/Squid_Integration_with_FreeIPA_using_Single_Sign_On
> I had setup squid.
>
> Tonight running the updates the changes to the init script
>
http://freei
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2013 01:17 PM, Simo Sorce wrote:
> On Wed, 2013-03-13 at 12:41 +0000, Dale Macartney wrote:
>> chown root:mail /etc/postfix/smtp.keytab
>> chmod 644 /etc/postfix/smtp.keytab
>>
> NEVER ever use 644 on a keytab file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/13/2013 10:47 AM, Dale Macartney wrote:
>
>
> On 03/12/2013 02:05 PM, Anthony Messina wrote:
> > On Tuesday, March 12, 2013 08:53:59 AM Anthony Messina wrote:
> >> On Tuesday, March 12, 2013 01:50:47 PM Dale Macartney
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/12/2013 02:05 PM, Anthony Messina wrote:
> On Tuesday, March 12, 2013 08:53:59 AM Anthony Messina wrote:
>> On Tuesday, March 12, 2013 01:50:47 PM Dale Macartney wrote:
>>> > # Import environment f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/2013 02:34 PM, Anthony Messina wrote:
> On Friday, March 08, 2013 08:09:20 AM Loris Santamaria wrote:
>>> 2. Kerberos / GSSAPI (I heard SASL can be used here as well ) for
>>> authenticated SSO mail sending
>>
>> Create the service in ipa, "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2013 11:39 AM, Christian Horn wrote:
>
>
>
> Dale Macartneyさんが書きました:
>>
>> On 03/11/2013 11:04 AM, Christian Horn wrote:
>>>
>>> How about having service-add/ipa-getkeytab done on the server,
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2013 11:04 AM, Christian Horn wrote:
> Hoi,
>
> Dale Macartneyさんが書きました:
>>
>> I'm open to hear some opinions and thoughts on what the best way to
>> auto-provision service principles in an environment with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I'm open to hear some opinions and thoughts on what the best way to
auto-provision service principles in an environment with a 100%
autonomous build process..
Lets say for example, I wanted to provision a mail server and configure
dovecot SSO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/2013 02:34 PM, Anthony Messina wrote:
> On Friday, March 08, 2013 08:09:20 AM Loris Santamaria wrote:
>>> 2. Kerberos / GSSAPI (I heard SASL can be used here as well ) for
>>> authenticated SSO mail sending
>>
>> Create the service in ipa, "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/2013 12:39 PM, Loris Santamaria wrote:
> I can help you with items #1 and #2:
>
> El vie, 08-03-2013 a las 08:56 +0000, Dale Macartney escribió:
>> Hi all
>>
>> I've been reading through threads and thread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/2013 09:38 AM, Petr Spacek wrote:
> On 7.3.2013 18:06, Dale Macartney wrote:
>>
>> I have just updated the article to have dovecot automatically creating a
>> maildir in a custom location.
>>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I've been reading through threads and threads of mailing lists and
google search results on this but most of the documentation isn't very
specific and is just vague enough for me not to make any progress.
Would anyone be able to assist with t
Dale
>
> Regards,
> Johan.
>
>
> -
> *From:* freeipa-users-boun...@redhat.com
[freeipa-users-boun...@redhat.com] on behalf of Dale Macartney
[d...@themacartneyclan.com]
> *Sent:* Thursday, March 07, 2013 13:35
> *To:* freeipa-users@redhat.com
> *S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2013 02:33 PM, Johan Petersson wrote:
> Hi,
> I hope someone here can shed some light on what is wrong in my test
environment.
> The error seem to be that Dovecot on mail server wants to access mail
folder in my home directory on the NFS Ser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I've been trying to document the domain trust process for the past two
days and I am seeing the same results no matter the configuration.
Basically I have nuked and rebuilt my environment several times and all
yields the same results.
Steps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2013 02:46 PM, M.R Niranjan wrote:
> On 03/06/2013 08:03 PM, Johan Petersson wrote:
> > Hi,
> > I hope someone here can shed some light on what is wrong in my test
> > environment.
> > The error seem to be that Dovecot on mail server wants t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2013 02:58 PM, Guy Matz wrote:
> Hello! Does anyone out there run two instances of freeipa, prod & non-prod
> instances? Are there any
issues to be wary of in this scenario? Any gotchas? Do you use the same
realms & domain names between ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2013 11:15 AM, Jakub Hrozek wrote:
> On Mon, Feb 25, 2013 at 11:06:09AM +0000, Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On 02/25/2013 10:58 AM, Jakub Hroze
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2013 10:58 AM, Jakub Hrozek wrote:
> On Mon, Feb 25, 2013 at 10:30:44AM +0000, Dale Macartney wrote:
>>>> What state is your SELinux in? Permissive/Enforcing/Disabled ?
>> Another fail on my part. Works fine in permi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2013 10:15 AM, Jakub Hrozek wrote:
> On Sat, Feb 23, 2013 at 10:40:03PM +0000, Dale Macartney wrote:
>>
>
> On 02/23/2013 10:36 PM, Rob Crittenden wrote:
> >>> Dale Macartney wrote:
> >>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/23/2013 10:36 PM, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Even folks
>>
>> I've verified this both in a kickstart and via man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Even folks
I've verified this both in a kickstart and via manual install to verify
any user error on my part.
I have a clean installation of RHEL 6.4 for an IPA domain of example.com
I also have several clients which are also clean installs of rhel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/23/2013 09:47 PM, Dmitri Pal wrote:
> On 02/23/2013 12:48 PM, Dale Macartney wrote:
> >
>> Hi all
>>
>> I've just performed a clean IPA installation and noticed that if you're
>> using integrated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I've just performed a clean IPA installation and noticed that if you're
using integrated DNS, you are still unable to use bind in a chrooted
environment with a default IPA install.
Basically if its a chrooted environment, named will fail to s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2013 04:39 PM, Dmitri Pal wrote:
> On 02/10/2013 07:15 AM, Dale Macartney wrote:
> >
>> Hi all
>>
>> So I have started testing more of the end user experience of FreeIPA
>> with my integration docs of differ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
So I have started testing more of the end user experience of FreeIPA
with my integration docs of different services over the weekend and when
I logged in as an IPA test user to Jabber, I noticed that the user
details are not being populated.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/2013 09:51 PM, Steven Jones wrote:
> Hi,
>
> I have all done this, so from what you write I think IPA would be a
good fit for what you want, except that is the single sign on bit I have
not looked to see if that can be done. For http restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/2013 07:16 PM, Dmitri Pal wrote:
> On 01/19/2013 01:25 PM, MaSch wrote:
>> Hello all,
>>
>> I'm trying to setup FreeIPA on Fedora 18 (Final) with AD integration
on a test server. However I do not even get past
>> the initial (local) steps de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
So, basis of my testing environment is as follows
RHEL 6 running IPA 2.2 or 3.0 (Will be looking to test on both versions)
RHEL 6 and Fedora 18 workstations connected as ipa clients to IPA domain.
I am using this article in place with m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/02/2013 12:42 AM, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On 01/01/2013 11:42 PM, Rob Crittenden wrote:
>>> Dale Macartne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/01/2013 11:42 PM, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On 12/29/2012 06:38 PM, Rob Crittenden wrote:
>>> Dale Macartne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/29/2012 06:38 PM, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Afternoon all
>>
>> using Fedora 18 Beta and attempting to install FreeI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Afternoon all
using Fedora 18 Beta and attempting to install FreeIPA 3.1
when running through the install of "ipa-server-install --setup-dns" I
end up with a failure with the below output
[root@ds01 ~]# ipa-server-install --setup-dns
.
.
D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 01:20 PM, Simo Sorce wrote:
> On Wed, 2012-12-19 at 12:30 +0000, Dale Macartney wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Morning all
>>
>> Heres something I was wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
Heres something I was working on last night with Gavin Spurgeon.
If anyone would like to comment on better ways to achieve this, i'd love
to here it so I can update my own procedures (and the article of course)
https://www.dalemacartney
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 09:25 AM, Innes, Duncan wrote:
> Are there any results you can even talk about at this stage?
Although, not offical supported by Red Hat. Here's something I wrote for
my own environments. It is just a scripted tool to tar up what I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/12 13:39, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Afternoon all
>>
>> I have a demo lab set up with RHEV 3.0 and IPA running on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Afternoon all
I have a demo lab set up with RHEV 3.0 and IPA running on RHEL 6.3 (
ipa-server-2.2-16)
I have an api script that handles all my deployments and I am trying to
set up a role account for my script to run within a jenkins environment.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/12 16:22, John Dennis wrote:
> On 08/06/2012 11:07 AM, Dale Macartney wrote:
>> Although I can use any ldapmodify capable tool to do this, I was
>> wondering what the "recommended" way that we should be telling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Afternoon all
Although I can use any ldapmodify capable tool to do this, I was
wondering what the "recommended" way that we should be telling customers
who want to change OU trees?
e.g, say in a high school using IPA, they wished to create a parent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Duncan
I spent a substantial amount of time on restorations last week. I was
working towards a "System State Backup" method of backing up IPA.
I managed to get a restoration working on a completely clean system by
doing a file level restore.
Wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
I've just published a walk through on tapping the YubiRadius virtual
appliance into FreeIPA.
Target audience level : Beginner
Link to page is :
http://freeipa.org/page/YubiRadius_integration_with_group-validated_FreeIPA_Users_using_LDAP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/06/12 06:52, Sumit Bose wrote:
> On Wed, Jun 27, 2012 at 10:35:00PM +0100, Dale Macartney wrote:
>>
> Evening all
>
> I have just updated my local RHEL 6 repositories from 6.2 to 6.3 and
> installed a new ipa server in
4 463 6272
>
> ____
> From: freeipa-users-boun...@redhat.com
[freeipa-users-boun...@redhat.com] on behalf of Dale Macartney
[d...@themacartneyclan.com]
> Sent: Wednesday, 27 June 2012 11:27 p.m.
> To:
> Subject: [Freeipa-users] IPA Backup / Restore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
I have just updated my local RHEL 6 repositories from 6.2 to 6.3 and
installed a new ipa server in a test network.
I get the following errors now despite having a valid tgt. This worked
perfectly a few hours ago (before I updated the rep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy all
We have had quite alot of discussions on the list about this process but
I'd like to get some documentation together so we are all speaking the
same language.
So last night I wrote a script to backup IPA based on the below article.
https:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/06/12 22:37, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On 25/06/12 19:53, Rob Crittenden wrote:
>>> Dale Macartne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/06/12 19:53, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi all
>>
>> I have a RHEL 6.2 ipa domain and I am running through one of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I have a RHEL 6.2 ipa domain and I am running through one of my known
working kickstarts for kerberised squid but instead of using RHEL i'm
setting it up on Fedora 17.
I get the following error on the fedora system which has
freeipa-admintool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/06/12 18:24, Natxo Asenjo wrote:
> On Thu, Jun 14, 2012 at 12:54 PM, Dale Macartney mailto:d...@themacartneyclan.com>> wrote:
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I've just placed anothe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
I have to say I am a little disappointed with myself to be honest as I
thought I published this a while ago.
I've just placed another wiki article for adding Jabber services to IPA.
This is a work in progress as I'm aiming for SSO abilit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
I am trying to set up a stub zone from my IPA domain (example.com) to my
Windows domain (nt.example.com.
Network details as follows
example.com
managed by IPA server ds01.example.com 10.0.1.11
nt.example.com
managed by Win server dc01.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/12 23:50, Dmitri Pal wrote:
> On 06/01/2012 03:14 AM, Dale Macartney wrote:
> >
>>
>>
>> On 31/05/12 23:54, Dmitri Pal wrote:
>> > On 05/31/2012 03:03 PM, Dale
>> Macartney wrote:
>>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/12 14:21, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> On 05/06/12 14:09, Rob Crittenden wrote:
>>> Dale Ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/12 14:09, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi all
>>
>> I may be overlooking something here, but from what I can gather,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
I may be overlooking something here, but from what I can gather, the
value in the ipa config of "Default e-mail domain for new users" should
automatically create the mail attribute for said user upon creation?
Do I need to do an additional st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/06/12 18:28, Kline, Sara wrote:
>
> Some of my users have expressed concerns about moving to FreeIPA
because they prefer to use SSH. The main reason behind that is because
they can use agent forwarding and only have to sign on once. I did find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
Just a quick mail to to let everyone know that I have placed a new wiki
page for integrating Zimbra authentication and GAL lookups into IPA.
Link is here
http://freeipa.org/page/Zimbra_Collaboration_Server_7.2_Authentication_and_GAL_look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/12 20:31, Alexander Bokovoy wrote:
> On Sat, 02 Jun 2012, Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Evening all
>>
>> What's the recommended met
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
What's the recommended method for using service accounts with IPA?
For example, using a piece of software that needs to bind to LDAP (aka
Zimbra, Moodle, Joomla, etc), having a password expiry on that specific
bind user would result in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/05/12 23:54, Dmitri Pal wrote:
> On 05/31/2012 03:03 PM, Dale Macartney wrote:
> >
>> Evening all
>>
>> http://www.youtube.com/watch?v=uvfkj8V6ylM
>>
>> This video was floating around Google plus a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
http://www.youtube.com/watch?v=uvfkj8V6ylM
This video was floating around Google plus a few days ago which is
brilliant to show off RHEV's VDI technologies. I was wondering if anyone
has some a similar business case of vdi deployments wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/05/12 15:10, Simo Sorce wrote:
> On Thu, 2012-05-31 at 07:55 +0100, Dale Macartney wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>>
>> On 31/05/12 00:13, Dmitri Pal wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/05/12 00:13, Dmitri Pal wrote:
> On 05/30/2012 06:12 PM, Dale Macartney wrote:
> >
>> Evening all
>>
>> Has anyone dabbled with Zimbra integration with IPA as yet? I just had a
>> brief brainstorm moment of t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
Has anyone dabbled with Zimbra integration with IPA as yet? I just had a
brief brainstorm moment of thinking "Now that would be useful".
I'm curious to see if anyone else has tried it? Otherwise I'll give a go
and see what docs I can pro
ote:
>>>> On 05/22/2012 04:28 AM, Dale Macartney wrote:
>>>>> Dmitri, Rob
>>>>>
>>>>> I thought I might reply to you both directly, just in case others on
>>>>> the list vent frustrations on the ongoing discussion of this topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evening all
Does IPA currently accommodate for child domains? As in the equivalent
of Active Directory child domains?
I can't seem to find any documentation mentioning this..
Dale
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All
I have added a walk through on configuring Dovecot to use IMAPS with SSO
support to the Wiki.
http://freeipa.org/page/Dovecot_IMAPS_Integration_with_FreeIPA_using_Single_Sign_On
Feed back is more than welcome
Dale
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All
I have added a walk through on configuring Dovecot to use IMAPS with SSO
support to the Wiki.
http://freeipa.org/page/Dovecot_IMAPS_Integration_with_FreeIPA_using_Single_Sign_On
Feed back is more than welcome
Dale
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco
I had a very similar issue trying to do the same thing a while back on
the day RHEL 6.2 went GA..
My situation was
SElinux enforcing, then run ipa-server-install.. it gets half way
through the process and it fails
then I tried
SELinux pe
-Triggs wrote:
> On 02/09/2012 06:48 AM, Dale Macartney wrote:
>>
>> Morning all
>>
>> I have a working setup of ejabberd authenticated to pam on an IPA client
>> which works great.. However, unlike my other projects to provide
>> details of integration with I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
I have a working setup of ejabberd authenticated to pam on an IPA client
which works great.. However, unlike my other projects to provide
details of integration with IPA, I am struggling with the SSO aspect of
it, simply because of a lac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Morning all
I have a working setup of ejabberd authenticated to pam on an IPA client
which works great.. However, unlike my other projects to provide
details of integration with IPA, I am struggling with the SSO aspect of
it, simply because of a lac
ipa service-add HTTP/$(hostname)
I will be giving this a go for testing sake tonight.
Dale
On 02/08/2012 04:00 PM, Rob Crittenden wrote:
> Dale Macartney wrote:
>>
> Hi JR
>
> I agree with your statement of acceptable risk.. this is my main reason
> for questioning..
>
&
area of acceptable risk
with lots of compensating controls and logging.
>
>
> On Feb 8, 2012, at 6:44 AM, Dale Macartney wrote:
>
>>
> Hi Simo
>
> ipa-client-install is provided by the ipa-client rpm. Details below
>
> Name : ipa-client
> Arch : x86_64
> Version
after running ipa-client-install.
Does this help paint a picture?
Dale
On 02/08/2012 01:49 PM, Simo Sorce wrote:
> On Wed, 2012-02-08 at 11:13 +0000, Dale Macartney wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> morning all...
>>
>> i
in an environment of their own so
far?
Dale
On 02/08/2012 09:28 AM, Christian Horn wrote:
> On Wed, Feb 08, 2012 at 11:13:36AM +0000, Dale Macartney wrote:
>>
>> i'm dabbling with automated provisioning of ipa client servers, and i'm
>> a little perplexed on how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
morning all...
i'm dabbling with automated provisioning of ipa client servers, and i'm
a little perplexed on how to add a keytab to a system during the %post
section of a kickstart...
i've run ipa-client-install -U -p admin -w redhat123 which works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2012 08:13 AM, Natxo Asenjo wrote:
> On Fri, Feb 3, 2012 at 9:02 AM, Natxo Asenjo
wrote:
>> On Fri, Feb 3, 2012 at 8:31 AM, Dale Macartney
>> wrote:
>>
>>> I have been experimenting with how best
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2012 08:02 AM, Natxo Asenjo wrote:
> On Fri, Feb 3, 2012 at 8:31 AM, Dale Macartney
> wrote:
>
>> I have been experimenting with how best to address this, however I am
>> constantly being pushed back to the only wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Craig
I am actually working on this very thing at the moment.
there is a very basic config here
(http://freeipa.org/page/Dovecot_Integration), however this is using pam
for everything
The end goal of course is sso in which I have managed to get
01/31/2012 06:48 PM, Simo Sorce wrote:
> On Tue, 2012-01-31 at 18:22 +0000, Dale Macartney wrote:
>>
> All
>
> I just found the culprit for the selinux error
>
> I have the user's home dir automatically created when I was testing
> the account was working.
>
> s
s set to
home_root_t instead of user_home_dir_t.
once a restorecon was run on /home (restorecon -R /home) the selinux
errors disappeared when accessing mail via imap.
I'll do a write up of the details for the wiki so it is documented.
Dale
On 01/31/2012 04:40 PM, Dale Macartney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thanks Siggi,
I was just browsing past those mails from earlier today as well... I'll
make those changes before it goes on the wiki.
On 01/31/2012 04:37 PM, Sigbjorn Lie wrote:
> On 01/31/2012 05:07 PM, Dale Macartney wrote:
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
howdy all
just another update from me.
I have a workable gssapi setup working with dovecot for imap... (i
didn't test pop yet).
the below setup was tested against rhel6.2
# enable dovecot on startup
chkconfig dovecot on
# set dovecot to listen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
;-) will do mate. I'm writing a list of items to cover at the moment
actually.
On 01/30/2012 08:02 PM, Dmitri Pal wrote:
> On 01/30/2012 02:50 PM, Dale Macartney wrote:
> >
>> Hey Erinn, funny you mention that actually,
cible configuration :-)
thanks for the positive feedback.
Dale
On 01/30/2012 07:41 PM, Erinn Looney-Triggs wrote:
> On 01/30/2012 10:20 AM, Dale Macartney wrote:
>>
>> Hi Erinn
>>
>> I originally asked the question as I was thinking my auth attempts were
>> failing wh
icate from dovecot and I was able to retrieve the mail as intended.
Does this help clear things up?
Dale
On 01/30/2012 07:11 PM, Erinn Looney-Triggs wrote:
> On 01/30/2012 07:42 AM, Dale Macartney wrote:
>>
>> Of course Dmitri
>>
>> Here you go. I was actually tr
1 - 100 of 104 matches
Mail list logo