[JBoss JIRA] (DROOLS-2860) Add second level header
by Juraj Soltes (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2860?page=com.atlassian.jira.plugi... ]
Juraj Soltes updated DROOLS-2860:
---------------------------------
Story Points: 3
> Add second level header
> -----------------------
>
> Key: DROOLS-2860
> URL: https://issues.jboss.org/browse/DROOLS-2860
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Labels: ScenarioSimulation
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Inside the grid, the scenario-specific columns are grouped in two categories: "Given" and "Expected".
> All the "Given" columns should go below the main "Given" header, and all the "Expected" ones below "Expected".
> For each column there should be, then, a specific header
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2903) Update test result panel with new UX/UI
by Daniele Zonca (JIRA)
Daniele Zonca created DROOLS-2903:
-------------------------------------
Summary: Update test result panel with new UX/UI
Key: DROOLS-2903
URL: https://issues.jboss.org/browse/DROOLS-2903
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing, Test Scenarios Editor
Reporter: Daniele Zonca
Assignee: Toni Rikkola
Update jUnit result test panel to new UX/UI in terms of feature and look and feel
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-9702) SSO Integration for Programmatic Authentication
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-9702?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse reassigned WFLY-9702:
--------------------------------------
Assignee: Darran Lofthouse
> SSO Integration for Programmatic Authentication
> -----------------------------------------------
>
> Key: WFLY-9702
> URL: https://issues.jboss.org/browse/WFLY-9702
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Security, Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
>
> At the moment the SSO integration only fully covers authentication mechanisms as they can be wrapped, we need to revisit for programmatic authentication.
> In this scenario we don't have either a wrapped mechanism or a CallbackHandler.
> Couple of options: -
> * Can we get away with pushing in some form of IdentityCache factory the mechs can obtain from the request? This may miss the additional notifications the SSO impl depends on.
> * Can we also better support listening for the notifications without the need for wrappers? This could cover both mechs and programmatic authentication?
> * Instead do we make the programmatic authenticator pluggable, i.e. push in an SSO aware impl, it can choose how to handle it's own caching and also doesn't need the notifications as it is in control of that stage of the process.
> *
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFCORE-4051) KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4051?page=com.atlassian.jira.plugi... ]
Martin Choma commented on WFCORE-4051:
--------------------------------------
[~chuffman] this effectively mean in FIPS mode reload truststore operation won't work. I think we should document that restriction. I think there is already general section about fips that advanced scenarios are not supported in FIPS mode. We should probably name this one explicitly.
> KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used
> -------------------------------------------------------------------------
>
> Key: WFCORE-4051
> URL: https://issues.jboss.org/browse/WFCORE-4051
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 6.0.0.CR2
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 6.0.0.CR3
>
>
> Creating 2-way SSL Context fails with error.
> {code}
> 12:04:28,689 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.ssl-context.ssl-context-client-cert: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.ssl-context-client-cert: java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used
> at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used
> at sun.security.ssl.SSLContextImpl.chooseTrustManager(SSLContextImpl.java:115)
> at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:78)
> at javax.net.ssl.SSLContext.init(SSLContext.java:282)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980)
> ... 9 more
> 12:04:28,690 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("server-ssl-context" => "ssl-context-client-cert")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.ssl-context-client-cert" => "java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used
> Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE TrustManagers may be used"}}
> {code}
> Seems DelegatingTrustManager is created always.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months