Return-Path: X-Original-To: apmail-ws-dev-archive@www.apache.org Delivered-To: apmail-ws-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9C29217649 for ; Mon, 3 Nov 2014 10:34:34 +0000 (UTC) Received: (qmail 49697 invoked by uid 500); 3 Nov 2014 10:34:33 -0000 Delivered-To: apmail-ws-dev-archive@ws.apache.org Received: (qmail 49552 invoked by uid 500); 3 Nov 2014 10:34:33 -0000 Mailing-List: contact dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ws.apache.org Delivered-To: mailing list dev@ws.apache.org Received: (qmail 49542 invoked by uid 99); 3 Nov 2014 10:34:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Nov 2014 10:34:33 +0000 Date: Mon, 3 Nov 2014 10:34:33 +0000 (UTC) From: "Colm O hEigeartaigh (JIRA)" To: dev@ws.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (WSS-518) WSConfig static initializer attempts to modify JCE Providers fail in JVM with restrictive security policies MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WSS-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-518. ------------------------------------- Resolution: Fixed > WSConfig static initializer attempts to modify JCE Providers fail in JVM with restrictive security policies > ------------------------------------------------------------------------------------------------------------ > > Key: WSS-518 > URL: https://issues.apache.org/jira/browse/WSS-518 > Project: WSS4J > Issue Type: Improvement > Components: WSS4J Core > Affects Versions: 2.0.2 > Reporter: Aaron Anderson > Assignee: Colm O hEigeartaigh > Fix For: 2.0.3 > > > I am attempting to use WSS4j 2.0.2 to perform WS-Security x509 signatures on XML DOM objects in a restrictive Cloud based JVM environment. When I attempt to sign a document the org.apache.wss4j.dom.WSConfig class gets initialized and it has a static initializer to load several JCE libraries. Because the JVM SecurityManager has restrictive polices defined any attempts to read system properties or modify JCE providers are denied and the class fails to load. The org.apache.wss4j.common.crypto.WSProviderConfig class has a setAddJceProviders and I think the WSConfig class should honor that setting. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org For additional commands, e-mail: dev-help@ws.apache.org