[midPoint] inducement issue after upgrade to 3.7

[Pavol Mederly]

Hello Davy,

this is really interesting. Have you found anything in the meanwhile?

If not, we can diagnose it using the brutal force: you could set the 
logging of Model (the whole component), Projector, and Clockwork to 
TRACE, do an import of a single user, and send the zipped log either 
here or to support at evolveum.com. We could have a look at that.

Pavol Mederly
Software developer
evolveum.com
  

On 29.01.2018 13:54, Davy Priem wrote:
>
> Hi Ivan,
>
> Thank for your response. The role has an inducement for AD. I don’t 
> see any errors in the log, but when a new account is created, I do see 
> the normal AD LDAP warning stuff, so midpoint is definitely doing 
> something. User is not created though. I’ll try some more debugging. I 
> also included the role as attachement.
>
> AD LDAP warnings:
>
> 2018-01-29 13:30:39,000 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,000 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.12, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,000 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.2.840.113556.1.4.906, cannot 
> determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.15, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,001 [] [midPointScheduler_Worker-1] WARN 
> (com.evolveum.polygon.connector.ldap.schema.AbstractSchemaTranslator): 
> method: null msg:Uknown attribute 1.3.6.1.4.1.1466.115.121.1.27, 
> cannot determine if it is binary
>
> 2018-01-29 13:30:39,040 [] [midPointScheduler_Worker-1] INFO 
> (org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean): 
> Creating Service 
> {http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd}WinRmService from 
> WSDL: 
> jar:file:/var/cache/tomcat/temp/bundle-1680891419/lib/winrm4j-client-0.4.0.e4.jar!/wsdl/WinRmService.wsdl
>
> *Van:*midPoint [mailto:midpoint-bounces at lists.evolveum.com] *Namens 
> *Ivan Noris
> *Verzonden:* Wednesday, 24 January 2018 09:43
> *Aan:* midpoint at lists.evolveum.com
> *Onderwerp:* Re: [midPoint] inducement issue after upgrade to 3.7
>
> Hi Davy,
>
> I have just tried our training environment installed from scratch, 
> where we assign a role using object template, to each newly imported 
> person from HR source. And it works. The projections are created after 
> role is assigned.
>
> I have not clean 3.7 but 3.7-support branch to be honest.
>
> Are there any errors in midpoint.log? Can you share the role?
>
> Best regards,
>
> Ivan
>
> On 24.01.2018 09:17, Davy Priem wrote:
>
>     Hi,
>
>     This is a probably a version stupid question, but since I upgraded
>     to version 3.7, the inducements on a role aren’t processed anymore
>     when a role is assigned to a user. I have a template that assigns
>     a role on a new user. That role has several inducements. When a
>     new users is imported, midpoint succesfully assigns the role to
>     the user (as with 3.6). However, there it stops. When I go to the
>     user and do a recon, then the projections are made. Am I
>     overlooking something? I didn’t found any behaviour change in 3.7
>     release notes.
>
>
>
>     Best regards,
>
>     Davy Priem
>
>
>
>
>     _______________________________________________
>
>     midPoint mailing list
>
>     midPoint at lists.evolveum.com <mailto:midPoint at lists.evolveum.com>
>
>     http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
> -- 
> Ivan Noris
> Senior Identity Engineer
> evolveum.com
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180207/c861ec98/attachment.htm>