Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install Error AzureADB2CProvider:Cannot insert duplicate key row #19

Closed
moorecreative opened this issue May 15, 2020 · 10 comments
Closed

Comments

@moorecreative
Copy link

I encountered an installer issue, though I am not sure it impacted the function of the authentication module as it completed installation enough to be listed within the Installed Authentication Systems list.

Scenario Environment - Evoq 9.4.4
Module Version - DNN Azure Active Directory B2C Provider 1.4.3
Module Version - DNN Azure Active Directory Provider 4.0.1

Install Error Event
In my testing scenario, I have the 4.0.1 DNN Azure Active Directory Provider is already installed in the DNN instance BEFORE the B2C Provider, however I do not think necessarily that it was involved in this specific install error message. I believe that the installer is twice trying to set a database record in the IX_Packages table. The following error is displayed during the installation log:

AzureADB2CProvider:Cannot insert duplicate key row in object 'dbo.Packages' with unique index 'IZ_Packages'. The duplicate key value is (Intelequia,AzureADB2CProvider, Module, 1.4.3). The statement has been terminated.

Screenshots
image

image

@an-d-uu
Copy link
Contributor

an-d-uu commented Mar 16, 2021

The issue seems to be with the 2 modules that have the same name in the AzureADB2CProvider.dnn file. Is there any reason we can't name the second one something like AzureADB2CProvider_Impersonation?

image

@devtpsingh
Copy link

i am also facing the same issues, but whenever i refresh the page it's showing B2C provider and after configuration it's not working, please help me on this.

@davidjrh
Copy link
Member

Hi, yes, sounds like an issue with the package name with the Impersonation module. I'm going to fix the manifest file as suggested. But I suspect that has nothing to do with the @devtpsingh is experiencing after the installation, since if you are not using the Impersonation module, you should be fine. What's the other error @devtpsingh ?

@devtpsingh
Copy link

i am using DNN Evoq Content v. 09.06.01. i need to authenticate using Azure B2C. i tried installing B2C Provider version https://github.com/intelequia/dnn.azureadb2cprovider/releases (Trying v1.4.6, v1.4.5, v1.4.3 and v1.4.2) all the versions but facing same issues.
image

@devtpsingh
Copy link

After above error I checked with refresh the page and found B2C provider is showing on DNN Evoq setting tab.
I configure with all details and trying to login with B2C user and it's redirect to me on Azure Portal and asking to username and password. After login it's redirect to me on website but Login and Register button still on my website. Redirect URL is
image

@davidjrh
Copy link
Member

New release v1.4.7 solving this installation issue.

For the other @devtpsingh I need more details. I see the redirected URL is missing the "/login". Did you put something on the ReturnURL field in the B2C settings in DNN? If you are not sure about that config setting, leave it empty to allow the redirection to the default /login page.

@davidjrh
Copy link
Member

Hi @devtpsingh, seems your issue is not related to this issue subject, but let's try to figure out the reason:

  1. Your screenshot above is not from the v1.4.7, probably because the javascript client files were cached by your browser from a previous install. Please clear the browser cache or open an inprivate browser session. You should see some of the latest settings such as the "Auto-Authorize Users After Login"
    image
  2. Check the log files under /portals/_default/logs to see if there is any auth error.

@davidjrh
Copy link
Member

Going to close this issue since the subject has been resolved on v1.4.7. @devtpsingh please create another issue when having more information about your second error.

@devtpsingh
Copy link

yes, it's working for me.
thank you for help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants