v0.4.1-beta (Fortify SSC update)

This is a minor update to address the issue brough up in #4 .

v0.4-beta (Fortify SSC)

The most recent version of the connector (v0.4.x) has undergone a major rewrite in order to:

• Migrate the project to using VS Code in stead of Visual Studio
• Consolidate the code for the connectors for SSC and FoD, into a single project which will produce a single MEZ connector file.

SSC usability notes:

• There is no option to authenticate with user credentials. Only API keys can be used

FoD usability notes:

• "FoD Basic Login" will not work for tenants with multi-factor authentication (MFA) enabled. If MFA is enabled, you will need to use "Client ID & Secret" to authenticate.
• The Fed instance of FoD is not supported as I do not have access to that instance to test. If you need support for this, contact me directly and I'll try and offer assistance to you to add in support yourself.

v0.3-beta (Fortify SSC)

Changed how the URL can be specified. This time, if you have "/ssc" in the url (or some other value for the base url) then you'll need to specify that. Example url that you'd now need to provice is "https://localhost:8080/ssc".

v0.2-beta (Fortify SSC)

This is a minor update to fix a bug with the connector for the Fortify SSC connector when connecting to a SSC server with HTTPS enabled.

First beta release! v0.1-beta

This is an initial beta release of Power Query (Power BI) connectors for:

• Fortify SSC
• Fortify on Demand - AMS
• Fortify on Demand - EMEA
• Fortify on Demand - APAC