0
Fixed

Google passwords are not being set on creation

Boyd Bostock 7 years ago in UNIFYBroker/Google Apps updated by Adam van Vliet 7 years ago 6

Google passwords are not being set on creation, subsequent resets in AD are synchronised successfully.

In MIM the export_password attribute is set with the desired password, I was unable to find any information about this attribute or how to configure the Password Script in the Google Connector.

Unsure of when this started to re-occur as most users authenticate via the IDP, however Chromebooks authenticate directly. It appears this issue has occurred before https://voice.unifysolutions.net/communities/6/topics/2816-passwords-are-not-set-on-google-account-creation however the key is configured to be email address.

Identity Broker: v5.2.0 Revision #3
Google Connector: 5.2.0.2
Unify.IdentityBroker.Communicator.Google.dll: 5.2.0.1

Answer

Answer
Fixed

So just confirming, using the Identity Broker version of the Newtonsoft fixes that particular issue? I'll update the connector to use the same version so that it isn't able to override it.

Do you have an update on whether the password change is working?

Under review

The fix doesn't appear to have made it back to the main branch. I'll merge it up and get you a patch.

Under review

There were too many files touched in the merge to create a patch. Please try Identity Broker 5.2.2 RC1.

Applied the upgraded version of Identity Broker and it is now setting the password or creation.

An error was encountered with the updated version of Newtonsoft.Json.dll when starting Identity Broker service (Event Log entry below). Replacing the Newtonsoft.Json.dll (7.0.1.18622) file with the one from the previous version allowed IdB to start.

Service cannot be started. Unify.Framework.UnifyServiceStartException: Method not found: 'Newtonsoft.Json.JsonSerializerSettings System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.get_SerializerSettings()'. ---> System.MissingMethodException: Method not found: 'Newtonsoft.Json.JsonSerializerSettings System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.get_SerializerSettings()'.

   at Unify.Framework.Api.ApiWebAppStartupBase.Configure(IAppBuilder appBuilder, IDictionary`2 registeredControllers, IEnumerable`1 registeredApiDocumentation, IApiConfiguration apiConfiguration, Boolean forClientGen)
   at Unify.Framework.Api.ApiImplementation.<>c__DisplayClass13_0.<StartApiInner>b__0(IAppBuilder builder)
   at Microsoft.Owin.Hosting.Engine.HostingEngine.Start(StartContext context)
   at Unify.Framework.Api.ApiImplementation.StartApiInner(IApiWebAppStartup startup, IDictionary`2 registeredControllerFactories, IEnumerable`1 registeredApiDocumentation)
   at Unify.Framework.Api.ApiImplementation.StartApi(IApiWebAppStartup startup, IDi...

Sorry about that, not sure how it happened as it was branched from tested working branch. I'll take a look.

Answer
Fixed

So just confirming, using the Identity Broker version of the Newtonsoft fixes that particular issue? I'll update the connector to use the same version so that it isn't able to override it.

Do you have an update on whether the password change is working?

Hi Adam

The install of Identity Broker or the Google Apps for Identity Broker installed a newer version of which Newtonsoft.Json.dll resulted in the error, I do not know the exact version. I copied the version from the previous installation (7.0.1.18622) and there was no longer any errors.

The change has fixed the issue with the passwords and I have not noticed any other issues since the updade.

Boyd