Hey Marco, I hope you are still around, I was hoping to clear a few things up. First, on the link you provided, that goes to the setup to 2018. When I click the link to see the instructions for 2017: learn.microsoft.com/.../authenticating-users-with-active-directory-federation-service-2017 and that is the document I have been referencing the whole time, it says in the beginning that NAV 2017 with no CUs is compatible. Is that not the case? I got the ok to install the latest CU but I have to wait for a lot of red tape still. I'd like to get this working but if I can't on CU 3, it is what it is.
Also, it's sort of neither here nor there, but I'm very familiar with AD, it's just ADFS I'm not very learned in. I suppose that's 2 out of components at play but I still gotta try. That is my attempt at convincing you that replying to me isn't futile.
The 2 settings you mention are set. I even setup a separate non-prod instance in NAV so I could tinker more. I have the CredentialType set to AccessControlService and the 2 above settings set for the instance server config. I also have everything in the web.config set for the new instance I setup there as well. But I'm still being told by nav my user doesn't exist.
I have also triple checked that on my user config page in NAV under the Office 365 Authentication tab has my email address in the auth email. And I'm still getting these errors:
Server instance: NavTestCon
Tenant ID: <ii><ii>default</ii></ii>
<ii>You do not have access to Microsoft Dynamics NAV. Verify that russtoleum@contoso.com is set up as a valid Microsoft Dynamics NAV user.</ii>
Server instance: NavTestCon
Tenant ID:
<ii>Received security token, which could be validated, but which does not give access to Microsoft Dynamics NAV.
Issuer: nav.contoso.com/.../trust
Expiry (UTC): 12/19/2022 8:11:23 PM
Claims in token:
schemas.xmlsoap.org/.../name: russtoleum@contoso.com
schemas.microsoft.com/.../objectidentifier: S-1-5-21-1757981266-2052111302-0000000000-00000
schemas.microsoft.com/.../authenticationmethod: urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
schemas.microsoft.com/.../authenticationinstant: 2022-12-19T19:11:23.819Z
</ii>
As soon as I turn the cred type to Windows, i can login fine. This feels like either ADFS is sending the wrong info to NAV, are I am missing a setting somewhere.
What is frustrating for me is of course my ignorance of NAV. The instructions clearly say I don't need Azure AD to make this work, but I have to use the same settings as if I was setting up with Azure.
Also, this error looks like it might have something to do with the problem.
Server instance: NavTestCon
Tenant ID:
<ii>User:
Type: System.ObjectDisposedException
Message:
<ii>Cannot access a disposed object.
Object name: 'internalDictionary'.</ii>
ObjectName: internalDictionary
StackTrace:
at Microsoft.Dynamics.Nav.Runtime.DisposedImmutableDictionary`2.ContainsKey(TKey key)
at Microsoft.Dynamics.Nav.Runtime.NavTenantCollection.CheckAddTenant(String tenantId, IEnumerable`1 alternateIds)
at Microsoft.Dynamics.Nav.Runtime.NavTenantCollection.AddTenant(NavTenantSettings tenantSettings, Boolean overwriteTenantIdInDatabase, Boolean verifyDatabaseConnection, Boolean verifyServerInstanceKey, Boolean setSingleUserWhileOverwritingTenantId)
at Microsoft.Dynamics.Nav.Runtime.NavTenantCollection.ConfigureTenants(ServerUserSettings settings)
at Microsoft.Dynamics.Nav.Runtime.NavTaskFactory.<>c__DisplayClass11_0.<StartNewTask>b__0()
at System.Threading.Tasks.Task.Execute()
Source: Microsoft.Dynamics.Nav.Ncl
HResult: -2146232798
</ii>
Thanks for the info so far and any new direction you can give me. Even if it's just to say 'give up'.
