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

Fortify scan is not supported #386

Open
vijaybhas opened this issue Nov 10, 2021 · 2 comments
Open

Fortify scan is not supported #386

vijaybhas opened this issue Nov 10, 2021 · 2 comments

Comments

@vijaybhas
Copy link

Problem statement :
nar-plugin is not being supported with Fortify scan

Description:
by using nar-plugin for C++ files compilation for preparing Binaries
the compile options includes files linking options libraries in pom.xml
now for Fortify Scan it became ecessary to duplicate the efforts of providing same options explcitely for fortify scan as Fortify scan is not consuming the options in pom.xml

Fortify scan details:
sourceanalyzer –debug –verbose –logfile translate.log -b my_proj touchless mvn com.fortify.sca.plugins.maven:sca-maven-plugin:21.1.1:translate

[warning] nar type is not supported

let us know if any more details are requied

@vijaybhas
Copy link
Author

vijaybhas commented Nov 10, 2021

Additonal/Fortify Plugin Details :

			<build>
				<plugins>
					<plugin>
						<groupId>com.fortify.sca.plugins.maven</groupId>
						<artifactId>sca-maven-plugin</artifactId>
						<version>21.1.1</version>
						<executions>
							<execution>
								<goals>
									<goal>clean</goal>
									<goal>translate</goal>
									<goal>scan</goal>
								</goals>
							</execution>
						</executions>
					</plugin>
				</plugins>
			</build>

@GregDomjan
Copy link
Member

@vijaybhas The nar-maven-pluggin doesn't call on the sca-maven-plugin, and so this project configuration doesn't relate here.
You would need to raise issues with the sca-maven-plugin with ?SCA however I don't know where that would be from as the meta info in maven repo lookup is lacking.

To configure for the nar plugin to include the fortify prefix command you would include the fortifyID setting
It also expects that fortify is configured with licence and on the system path

			<plugin>
				<groupId>com.github.maven-nar</groupId>
				<artifactId>nar-maven-plugin</artifactId>
				<configuration>
					<fortifyID></fortifyID>

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

2 participants