Re: [389-users] Self Service Portal
We've been using this:http://code.google.com/p/pwm/De: "Paul Robert Marino" prmari...@gmail.comPara: "General discussion list for the 389 Directory server project." 389-users@lists.fedoraproject.orgEnviados: Lunes, 29 de Julio 2013 2:20:41Asunto: Re: [389-users] Self Service PortalIn the inexpensive commercial zone I've used something called password manager pro which also maintains per user and enterprise wide password vaults.The other thing I've done is written simple Perl CGI pages that do the email confirmation thing using a double email system the first using an auth code stored with a short timeout in memcached for confirmation then emails a second email includes GPG encrypted temporary random password with the GPG decryption code on the page from the first approval confirmation page.-- Sent from my HP Pre3On Jul 26, 2013 10:56, harry.dev...@faa.gov harry.dev...@faa.gov wrote: We use Self Service Password from the LDAP Tool Box project. Works pretty well for us. http://ltb-project.org/wiki/documentation/self-service-password Harry From:Tom Tucker tktuc...@gmail.com To:389-users@lists.fedoraproject.orgDate:07/26/2013 10:48 AMSubject:[389-users] Self Service PortalSent by:389-users-boun...@lists.fedoraproject.org Any recommendations on a commercial or open source web based self service portal to allow 389 DS users the ability to recover or change their password? Thanks, Tom-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users --389 users mailing list389-users@lists.fedoraproject.orghttps://admin.fedoraproject.org/mailman/listinfo/389-users-- Juan Carlos Camargo Carrillo.@jcarloscamargo957-211157 ,650932877-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Re: [389-users] Removing non-existent instances
On 07/29/2013 09:52 AM, Tripp Holden wrote: They need to be removed from both the replication topology and the console as none of the configuration was removed prior to the servers being brought offline. For console, you can use the console to remove the instances - in the topology view, right-click on the server instance, and select Remove. For replication, you'll have to remove all of the replication agreements on other servers that point to the server you removed, then you'll have to run the CLEANALLRUV task to clean up any remaining meta-data. https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Solving_Common_Replication_Conflicts.html#cleanruv -Tripp On Mon, Jul 29, 2013 at 10:47 AM, Rich Megginson rmegg...@redhat.com mailto:rmegg...@redhat.com wrote: On 07/29/2013 09:46 AM, Tripp Holden wrote: Hi guys, First time posting here. I recently inherited a 389 environment where two servers were taken down when we moved out of a datacenter and were not properly removed from the directory configuration prior to their removal. I've read through the remove-ds documentation and it seems to indicate that the command needs to be run from the instance server that is to be removed. Is there a recommended method for removing non-existent instances? Removing them from where? From the replication topology? From the console? Thanks! -Tripp -- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
