Forum Discussion
Within the gateway for a given data resource if I use windows auth upn's sometimes fail
So it seems like there may be a upn length limitation within the gateway/datasource, AD allows 1024 characters for the upn, I'm using about 30 characters. If I use a short upn it works if longer not sure what lenght it fails. when I look at the error details it shows the upn converted to a samaccountname. Is this a known issue that I missed.
lol the issue is not within the gateway process its a limitation of sql as far as I can tell, I don't think sql supports upn's. I never really paid attention to what sql does when you enter a upn for as a login id, it converts it to a samaccountname by looking up the name in AD, as far as I can tell, the issue being my accounts names may not be unique given the limitations of samaccountname character length. I think azure sql supports true upns. I have alternative methods to accomplish what I need but the names won't be as self describing.
1 Reply
lol the issue is not within the gateway process its a limitation of sql as far as I can tell, I don't think sql supports upn's. I never really paid attention to what sql does when you enter a upn for as a login id, it converts it to a samaccountname by looking up the name in AD, as far as I can tell, the issue being my accounts names may not be unique given the limitations of samaccountname character length. I think azure sql supports true upns. I have alternative methods to accomplish what I need but the names won't be as self describing.