search

dcwaterm / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

Macros do not work in New User Actions with Active Directory #503

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. add new user action to populate displayName
2. enter @LDAP:givenName@, @LDAP:sn@ as the attribute value
3. create a new user.  Display name will only have the comma in the field

This is an example.  I am not able to use any of the macros

What is the expected output? What do you see instead?
Need to be able to populate AD fields using Macros

What version of PWM are you using?
1.7.0

What ldap directory and version are you using?
Active Directory 2008 R2

Please paste any error log messages below:

Original issue reported on code.google.com by dpa...@bcidaho.com on 16 Oct 2013 at 2:23

Attachments:

GoogleCodeExporter commented 9 years ago 
Please try a daily build.

Original comment by menno.pi...@gmail.com on 26 Feb 2014 at 7:28

GoogleCodeExporter commented 9 years ago 
Menno

I tried last nights build and still have the same issue.
Can I provide any additional info?
Thanks

Original comment by dpa...@bcidaho.com on 27 Feb 2014 at 3:01

GoogleCodeExporter commented 9 years ago 
No, sorry... I was just asking to try the newest versions. There should be some 
improvements in there. 

I'll keep the ticket open for now.

Original comment by menno.pi...@gmail.com on 27 Feb 2014 at 3:05

GoogleCodeExporter commented 9 years ago 
Having an identical issue, can confirm. Setting fields (e.g. displayName) with 
static data results in correct setting of field, but macros do not work in the 
exact same situation (field shows blank).

Looks to be a known issue. Can anyone help?

Original comment by Tim.Fred...@gmail.com on 11 May 2014 at 9:38

GoogleCodeExporter commented 9 years ago 
I have the same problem on PWM version 1.7.1.
Any update for this ticket?

Original comment by Efrati.Y...@gmail.com on 1 Oct 2014 at 1:52

GoogleCodeExporter commented 9 years ago 
Its apparently was working in older releases 1.6.3, and I am having the exact 
same problem. This bug is a regression.

Original comment by automati...@gmail.com on 7 Dec 2014 at 5:39