Bug 1868074 - Error in security property. Constraint unknown: c2tnb191v1
Summary: Error in security property. Constraint unknown: c2tnb191v1
Keywords:
Status: CLOSED DUPLICATE of bug 1869017
Alias: None
Product: Fedora
Classification: Fedora
Component: java-11-openjdk
Version: 33
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-11 15:09 UTC by Lukáš Petrovický
Modified: 2020-09-15 16:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-15 16:11:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lukáš Petrovický 2020-08-11 15:09:15 UTC
Ever since this morning, I get the following issue when running Maven:
https://pastebin.com/yPh0acxM

Note the text at the end:
"Error in security property. Constraint unknown: c2tnb191v1"

This started happening this morning, when I updated my system and got this package:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1587614

At the same time, I also uninstalled this package, which made Maven switch from Java 8 to Java 11:
https://koji.fedoraproject.org/koji/packageinfo?packageID=15685

I tried switching Maven to OpenJDK 14, and the problem persisted.
This leads me to conclude it's not JDK-related, but rather something to do with system-wide crypto policies. But my knowledge in this area ends there.

Comment 1 Lukáš Petrovický 2020-08-11 15:12:21 UTC
The problem can be reproduced by running "mvn clean install -DskipTests" on the following Red Hat repo:
https://github.com/kiegroup/optaplanner

Alternatively, use my personal repo for possibly a slightly faster failure:
https://github.com/RoboZonky/robozonky

Comment 2 jiri vanek 2020-08-12 07:41:18 UTC
Can you please be more precise what versions worked and what not? 
From koji links it seems that it worked fine with jdk8 but not with jdk11, but in same paragraphthe crypto policies are mentioned.
Can you try: 
with jdk11 try different cryptopolicies? [ update-crypto-policies --set/get  LEGACY/DEFAULT/EMPT/FUTURE]
With jdk8 the same? You set back to jdk8 in jdk11 fedora by JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk ; considering it installed java-1.8.0-openjdk-devel and/or  alternatives --config java+javac to jdk8

On f32, where jdk8 is major. Does it work? How with different policies? And on f32, with jdk11 [JAVA_HOME=/usr/lib/jvm/java-11-openjdk ; considering it installed java-11-openjdk-devel,  alternatives --config java+javac to jdk11]

Thanx

Comment 3 Lukáš Petrovický 2020-08-12 08:45:54 UTC
OK, some more data. I've installed java-1.8.0-openjdk-devel and made it my default:

    [root@degrasse ~]# alternatives --display java
    java - status is manual.
     link currently points to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.272.b01-0.0.ea.fc33.x86_64/jre/bin/java

However, Fedora Maven still somehow uses Java 11:

    [triceo@degrasse robozonky]$ mvn -X
    Apache Maven 3.6.3 (Red Hat 3.6.3-4)
    Maven home: /usr/share/maven
    Java version: 11.0.9-ea, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.1-0.1.ea.fc33.x86_64

I can no longer uninstall Java 11, as that would uninstall Maven as well. (Maven in Fedora 33 now depends on Java 11.)
Is there a way to force Maven in Fedora to use the system's default Java?

I tried to set crypto policies to DEFAULT, EMPTY, FUTURE and LEGACY, the problem did not go away.
I don't have a way of checking this on Fedora 32. Even if I did, the Maven there does require Java 8 and not Java 11.

Comment 4 Lukáš Petrovický 2020-08-13 07:31:56 UTC
I've been fiddling with JAVA_HOME paths and the problem appears to have gone.
I'd have closed this issue, only I don't have the option to change status.

Comment 5 Severin Gehwolf 2020-09-15 16:11:11 UTC
These two bits gave it away:

Java version: 11.0.9-ea, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.1-0.1.ea.fc33.x86_64

and:

Error in security property. Constraint unknown: c2tnb191v1

This is a duplicate of bug 1869017. Marking as such. 11.0.9+6 should solve your problem.

*** This bug has been marked as a duplicate of bug 1869017 ***


Note You need to log in before you can comment on or make changes to this bug.