-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
On Mon, Mar 11, 2013 at 01:21:26AM -0400, Tim Hildred wrote:
> It definately wasn't a policy problem. I couldn't even use ipa passwd as
> admin from the command line, there was a connection error. The upgrade meant
> my IPA server was straight borked. The solution? Revert to a previous
> snapsho
Hello David,
I am still not convinced that this issue is not caused by a DNS. This is what
we do in "ipa" command:
1) We try to primarily connect to server that is defined in
/etc/ipa/default.conf in "server" option
2) If it is not available, we try to fallback to other IPA servers which are
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 100%
> autonomous build process..
>
> Lets say for example, I wanted to provision a mail server and configure
> dovecot SSO in the sam
-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 100%
>> autonomous build process.
Dale Macartneyさんが書きました：
>
> On 03/11/2013 11:04 AM, Christian Horn wrote:
> >
> > How about having service-add/ipa-getkeytab done on the server,
> > and having the keytab deployed onto the clientsystem using scp from
> > the server, or via configmanagement?
> That definitely gets around securit
-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,
>>> and having the keytab deployed onto the clien
Tim Hildred wrote:
It definately wasn't a policy problem. I couldn't even use ipa passwd as admin
from the command line, there was a connection error. The upgrade meant my IPA
server was straight borked. The solution? Revert to a previous snapshot, and
continue using the old, working IPA (2.0.
On 03/11/2013 07:43 AM, Dale Macartney wrote:
>
>
> 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,
> >>> and having the keytab deployed
Uzor Ide wrote:
Hi All
I upgraded fedora 17 with freeipa server to fedora 18, afterwards the
webui now comes back with error for every login attempt.
Error dialog box reports IPA Error 903
description: An internal error has occured.
Checking the /var/log/httpd/error_log, shows
7451 2013] [:er
Here is the output of the dig command. Cyclone does show up here , but our
networking people say there are no srv records in our current db. I still
think the trouble I am having has to do with the Internal Server Error I get
when I run ipa commands.
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc
On 03/11/2013 02:05 PM, David Fitzgerald wrote:
Here is the output of the dig command. Cyclone does show up here , but our
networking people say there are no srv records in our current db. I still
think the trouble I am having has to do with the Internal Server Error I get
when I run ipa co
David Fitzgerald wrote:
Here is the output of the dig command. Cyclone does show up here , but our
networking people say there are no srv records in our current db. I still
think the trouble I am having has to do with the Internal Server Error I get
when I run ipa commands.
There are two
13 matches
Mail list logo
