Connect with AD user to NetServer

lock
push_pin
done
Beantwoord
4

I have a problem connecting to the NetServer when I use AD login, SoUsers works fine. To connect to the NetServer I use:

services = new ServiceCollection();
services
	.AddNetServerCore<ProcessContextProvider>(options => {
		options.UseOnPremAD(); // See config section: ActiveDirectoryCredentialPlugin
	})
	.AddSoDatabase()
	//.AddSingleton<ILogger, SuperOffice.Logging.SoLogger>()
	.AddSingleton<IContextInitializer, ContextInitializer>()
	;

provider = services.BuildServiceProvider(true);
provider.RegisterWithNetServer();

But it can't atenticate with user/password. A funny thing is that the code (in a web.backend) connects without even the UseOnPremAD() option, BUT with a <USEC> from a web-panel.

Has anyone experience with UseOnPremAD() option or simular?

23 feb. 2024 | 12:11 p.m.

Alles Antwoorden (4)

Hi Martin!

Unfortunately the team hasn't documented these things. Looking at the implementation, it looks like UseOnPremAD just adding support for implicit windows users

So, with that enabled, I suppose you would be able to say SoSession.Authenitcate(); and NetServer would try to authenticate the current windows user.

So, in your scenario, authenticating with a username and password, this option is not necessary.

Best regards.

27 feb. 2024 | 11:32 a.m.
OK, thank you, it makes it easier of cause (for the user). I'll test it tomorrow or next week.
29 feb. 2024 | 06:22 a.m.

With the help from Tony, we manage to get it to work.

Add "SuperOffice.Onsite.dll" to the dynamic load list, this makes it work for 10.2.5 but for 10.2.9 you will need to add "SuperOffice.CRMScript.RTE.Client.dll" to the bin folder, as well. The file can be found in a SuperOffice CRM installation.

5 mrt. 2024 | 10:23 a.m.
SuperOffice.CRMScript.RTE.Client.dll is added to the nuget package from 10.3.3.
5 mrt. 2024 | 11:24 a.m.

Reply toevoegen