If you have Windows Integrated Authentication enabled, then it will not be possible to do this. The 401 is occurring before the request even makes it to ProGet, which is how WIA is designed. You can also set up a second site in IIS without WIA enabled. That would lalow the request to get to ProGet, and if you have an "Anonymous" pseudo-user configured with permissions, then the lack of a credential will be ignored.

Please disregard now. It's all working fine. Someone changed the issues I was seeing in Jira yesterday and moved them to another release, incorrectly, at about the same time I was viewing them. I got the legacy aspect figured out as well so all of future configs should be non-legacy. Thanks.

This is not currently supported. If you are a component company, you may want to contact us to see about partnering. We work with a handful of component vendors who use ProGet as a "back/middle-end" and then have a very simple customer-facing front-end on top of ProGet that integrates with their CRM, authentication, etc.

Hi, great question; yes, that would be doable through the API, but we're still putting the final touches on that. The "full API" would necessarily expose the entire complex model that's used behind the scenes (e.g. differentiating between jobs, job templates, and executions, etc), which from our experience is a real pain to work with, because it requires you to become experts of the domain model. Then you have to authenticate to it, etc. So, perhaps we'll also have a more intuitive API that looks a lot more like the web interface, and exactly like you said, has a simple url for a "kick me now" button of sorts. In the mean time, i'd definitely check it out to see how close it is to your requirements, and we would be happy to work with you to get a PoC going. It's still 1.0, but that's how we improve and get to 2.0 and so forth :)

Hi Byron - We do have a number of BuildMaster users who utilize the "Attach Build Report Action" to capture the output of a Fortify Static Code Analyzer scan after running it via the command-line; it's a general-purpose Action that will basically attach the report to the build so that everyone has visibility on the scan. Others will use Coverity for static analysis in the same manner. It would be relatively easy to build a "first-class" extension for Fortify, and as an enterprise customer, we'd be happy to work closely with you develop one should you want a bit tighter integration. Cheers, Alana

You can add an ExtensionIconAttribute assembly attribute to your extension for a custom logo that accepts a URL to the image in its constructor. Note that this attribute requires the BuildMaster SDK v4.1 or later. If you want to embed your image directly, you can convert the URL to a base64 string and embed it using a tool like this one: http://webcodertools.com/imagetobase64converter