-
Notifications
You must be signed in to change notification settings - Fork 53
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
Archimate CoArchi SSL issue #113
Comments
This is most certainly related to one missing certificate in your truststore. See this wiki page: https://github.com/archimatetool/archi-modelrepository-plugin/wiki/Use-SSL-TLS-with-local-or-private-PKI |
Thanks for the quick response and info. I followed the procedure to make Archi use OS certificate. Attached the Archi.ini after modifying. I restarted my laptop and tried again and received the same message. -clean I was going to try the other procedure but I am not sure what certificates should be exported from windows cert repository and imported into CACERTS used by the JRE Archi is using? |
The options to use a WINDOWS-ROOT trustStoreType have been provided by users on the forum:
I did test recently (windows 2010) and was not able to make it work, and thus went the cacert way (which I have been using for several years). I think we should go back to the forum (the first thred listed is the more recent) and see if someone can help you (and me) on this.
Usually you can simply connect to you git server in a browser and look at the certificate chain. Another option is to ask your IT guys which certificates are deployed on your workstation and needed for this server. |
I appreciate the help and for the lead on the additional discussion topics in the archimate forum. I will check out those topics. |
Hi JB, Can confirm that the following additions to Archi.ini seem to work great in my corporate network environment and Windows 10, thank you! I use this to reach out to a coArchi remote repository on dev.azure.com (Azure DevOps Repos) across our corporate proxy/firewall:
I'd even go so far as to recommend (or at least cast my vote that) these become the default Archi.ini options in your Windows build, if that's possible? This would follow the way (for example) web browsers seem to determine Trusted Root Certification Authorities on Windows, and therefore allow a single point of management for trusted root CAs on each corporate Windows machine, rather than also having to manage the various ..\jre\lib\security\cacerts files around the place. (such as C:\Program Files\Archi4\jre\lib\security\cacerts) Thanks, |
one last thing that may cause problem : if you changed your password and asked component to store it locally |
I've writen a path that allow to skip the SSL verfiction |
Looking for help resolving an issue with the COArchi plugin install on a Windows 10 device. When trying to do an initial import of a model from a git repository I am getting the following error? Using a vanilla install of Archimate (4.5.1) and the CoArchi plugin.
The text was updated successfully, but these errors were encountered: