-
Notifications
You must be signed in to change notification settings - Fork 156
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
CAPI Authentication Issues - New Installer #2057
Comments
As a temporary solution, we may wish to put harder protocol registers in for authenticating using the EDMC:// protocol. Longer-term solutions might include retiring that handler in favor of localhost default. I've been able to reliably recreate this occurrence and have some fixes in testing. Longer term solutions may need to be tested further. |
As per a 5.8.1 install, you should have registry keys under https://github.com/EDCD/EDMarketConnector/blob/develop/resources/EDMC_Installer_Config_template.txt#L71-L80 appears to be missing the IIRC, the ddeexec method is preferred over the |
Agreed with your diagnosis, came to that conclusion yesterday before work. PR opened for fix, is in testing right now. Aiming for fix release on Wednesday? Will see what tests show. |
Should be fixed. Will leave this open for 3 days for any follow-up issues before closing. |
The cAPI on the new installer in a small subset of users may have issues authenticating with the cAPI. This often can be identified in logs by a failed attempt to authenticate and lock the journal file, as seen here:
Originally posted by @connylindquist in #2048 (comment)
Current belief has this as an issue with the windows registry and protocol handling of the edmc://auth link and how FDEV hands us back the information.
The text was updated successfully, but these errors were encountered: