[jira] [Closed] (FC-264) Improve ACL in slapd test

[ https://issues.apache.org/jira/browse/FC-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-264. - > Improve ACL in slapd test > - > > Key: FC-264 >

[jira] [Closed] (FC-265) Delegated Administration Enhancements to Apache Fortress REST

[ https://issues.apache.org/jira/browse/FC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-265. - > Delegated Administration Enhancements to Apache Fortress R

[jira] [Closed] (FC-266) Delegated Admin - Fix inconsistent service to api mappings.

[ https://issues.apache.org/jira/browse/FC-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-266. - > Delegated Admin - Fix inconsistent service to api mappi

[jira] [Resolved] (FC-265) Delegated Administration Enhancements to Apache Fortress REST

[ https://issues.apache.org/jira/browse/FC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-265. --- Resolution: Fixed > Delegated Administration Enhancements to Apache Fortress R

[jira] [Resolved] (FC-266) Delegated Admin - Fix inconsistent service to api mappings.

[ https://issues.apache.org/jira/browse/FC-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-266. --- Resolution: Fixed > Delegated Admin - Fix inconsistent service to api mappi

[jira] [Closed] (FC-268) gid and uid number duplicates

[ https://issues.apache.org/jira/browse/FC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-268. - > gid and uid number duplicates > - > >

[jira] [Closed] (FC-269) Make Fortress ABAC Role Constraint multi tenant

[ https://issues.apache.org/jira/browse/FC-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-269. - > Make Fortress ABAC Role Constraint multi ten

[jira] [Resolved] (FC-268) gid and uid number duplicates

[ https://issues.apache.org/jira/browse/FC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-268. --- Resolution: Fixed > gid and uid number duplica

[jira] [Resolved] (FC-269) Make Fortress ABAC Role Constraint multi tenant

[ https://issues.apache.org/jira/browse/FC-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-269. --- Resolution: Fixed > Make Fortress ABAC Role Constraint multi ten

[jira] [Resolved] (FC-267) New Configuration entity

[ https://issues.apache.org/jira/browse/FC-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-267. --- Resolution: Fixed > New Configuration entity > > >

[jira] [Updated] (FC-269) Make Fortress ABAC Role Constraint multi tenant

[ https://issues.apache.org/jira/browse/FC-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-269: -- Description: Currently abac constraints depend on a global configuration property, stored like this: RC

[jira] [Created] (FC-270) Bump to LDAP API version 1.0.3

Shawn McKinney created FC-270: - Summary: Bump to LDAP API version 1.0.3 Key: FC-270 URL: https://issues.apache.org/jira/browse/FC-270 Project: FORTRESS Issue Type: Improvement Affects

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 18, 2019, at 3:49 PM, Stefan Seelmann wrote: > > Yes, the Jenkins machines are rather slow, I agree. > > There is a bit info (memory and disk) in the Jenkins wiki [1], our jobs > use the "ubuntu" label. For further info we need ask builds@a.o list. > > What's also possible, if you

Re: Opportunity to attend and speak ApacheCon

> On Apr 18, 2019, at 3:40 PM, Smith, Shawn Eion wrote: > > Hey Arkanshawn, > > Hope all's well. I talked to folks here and we would be willing to put > together a talk on Scimple. Any advice for this particular audience would be > greatly appreciated. > > Pennsylshawn Hey Pennsylshawn,

Re: Working on Fortress Docker Images / Builds / Jenkins tests

> On Apr 17, 2019, at 2:31 PM, Shawn McKinney wrote: > > That is to say, that running the test on a local VM finishes in < 10 minutes, > while in a Jenkins pipeline much longer, > 1 hour. It feels like the tests are running inside a VM that’s underpowered. The adds, u

Working on Fortress Docker Images / Builds / Jenkins tests

Hi, The docker images used by fortress to test openldap and apacheDS have been recently updated to support a minor change in the data schema, to support additional configuration params. https://hub.docker.com/r/apachedirectory/openldap-for-apache-fortress-tests/

Re: [VOTE] Release Apache LDAP API 1.0.3

> On Apr 17, 2019, at 6:29 AM, Emmanuel Lécharny wrote: > > Please cast your votes: > [ ] +1 Release Apache LDAP API 1.0.3 > [ ] 0 abstain > [ ] -1 Do not release Apache LDAP API 1.0.3 +1, download source bundle, built, passed all API tests. Next tested with fortress Core and apacheDS

[jira] [Created] (FC-269) Make Fortress ABAC Role Constraint multi tenant

Shawn McKinney created FC-269: - Summary: Make Fortress ABAC Role Constraint multi tenant Key: FC-269 URL: https://issues.apache.org/jira/browse/FC-269 Project: FORTRESS Issue Type: Improvement

[jira] [Commented] (FC-268) gid and uid number duplicates

[ https://issues.apache.org/jira/browse/FC-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817485#comment-16817485 ] Shawn McKinney commented on FC-268: --- depends on new configuration entity. > gid and uid number duplica

[jira] [Created] (FC-268) gid and uid number duplicates

Shawn McKinney created FC-268: - Summary: gid and uid number duplicates Key: FC-268 URL: https://issues.apache.org/jira/browse/FC-268 Project: FORTRESS Issue Type: Bug Affects Versions: 2.0.3

[jira] [Created] (FC-267) New Configuration entity

Shawn McKinney created FC-267: - Summary: New Configuration entity Key: FC-267 URL: https://issues.apache.org/jira/browse/FC-267 Project: FORTRESS Issue Type: Improvement Affects Versions

Opportunity to attend and speak ApacheCon

Hello, Later this year are two ApacheCon’s, one in Vegas (Sep 9-13), the other Berlin (Oct 22-24). First, if you are a committer on any project, There’s a deep discount for attendance. Second, if you’re selected to speak the fee is waived. Sometimes, speakers are provided travel stipend as

[jira] [Updated] (FC-247) Create a New Webapp to Manage Fortress Entities

[ https://issues.apache.org/jira/browse/FC-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-247: -- Fix Version/s: 2.0.4 > Create a New Webapp to Manage Fortress Entit

[jira] [Created] (FC-266) Delegated Admin - Fix inconsistent service to api mappings.

Shawn McKinney created FC-266: - Summary: Delegated Admin - Fix inconsistent service to api mappings. Key: FC-266 URL: https://issues.apache.org/jira/browse/FC-266 Project: FORTRESS Issue Type

[jira] [Commented] (FC-265) Delegated Administration Enhancements to Apache Fortress REST

[ https://issues.apache.org/jira/browse/FC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794269#comment-16794269 ] Shawn McKinney commented on FC-265: --- The ARBAC02 type of checks are optional and turned off by default

[jira] [Commented] (FC-265) Delegated Administration Enhancements to Apache Fortress REST

[ https://issues.apache.org/jira/browse/FC-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794267#comment-16794267 ] Shawn McKinney commented on FC-265: --- Changing the way Apache Fortress Rest accepts credentials for ARBAC02

[jira] [Created] (FC-265) Delegated Administration Enhancements to Apache Fortress REST

Shawn McKinney created FC-265: - Summary: Delegated Administration Enhancements to Apache Fortress REST Key: FC-265 URL: https://issues.apache.org/jira/browse/FC-265 Project: FORTRESS Issue Type

[jira] [Comment Edited] (FC-264) Improve ACL in slapd test

[ https://issues.apache.org/jira/browse/FC-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781692#comment-16781692 ] Shawn McKinney edited comment on FC-264 at 3/1/19 3:28 PM: --- The rationale

[jira] [Created] (FC-264) Improve ACL in slapd test

Shawn McKinney created FC-264: - Summary: Improve ACL in slapd test Key: FC-264 URL: https://issues.apache.org/jira/browse/FC-264 Project: FORTRESS Issue Type: Improvement Affects Versions

[jira] [Commented] (FC-263) Unable to resolve maven dependencies for fortress-core v2.0.3

[ https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749364#comment-16749364 ] Shawn McKinney commented on FC-263: --- You're welcome. Thanks for bringing it up. Would like to hear more

[jira] [Commented] (FC-263) Unable to resolve maven dependencies for fortress-core v2.0.3

[ https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749138#comment-16749138 ] Shawn McKinney commented on FC-263: --- Well that explains it.  Have never used/tested with Gradle. I'm fine

Re: Jenkinsfile and pipeline

> > On Jan 21, 2019, at 1:06 PM, Stefan Seelmann wrote: > > Let me know what you think or if you have objections or questions. > Otherwise I'd continue with more Jenkinsfiles :) +1, sounds like a great idea to me. Is this something we can divide and conquer? I’ve never done this, but it’s

[jira] [Commented] (FC-263) Unable to resolve maven dependencies for fortress-core v2.0.3

[ https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16744200#comment-16744200 ] Shawn McKinney commented on FC-263: --- > That dependency has been broken since ultimo 2015 how

[jira] [Assigned] (FC-263) Unable to resolve maven dependencies for fortress-core v2.0.3

[ https://issues.apache.org/jira/browse/FC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-263: - Assignee: Shawn McKinney > Unable to resolve maven dependencies for fortress-core v2.

Re: [VOTE] - Release Apache Kerby 2.0.0 - take II

+1 [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 5:25.228s [INFO] Finished at: Fri Jan 11 15:52:47 UTC 2019 [INFO] Final Memory: 93M/419M [INFO]

Re: [VOTE] Require Java 8 for Apache Directory projects

> On Jan 5, 2019, at 1:06 AM, Emmanuel Lécharny wrote: > > So I suggest we drop Java 7 as the base version for our project, and switch > to Java 8 (which is also EOLed, ftr). > > > [ ] +1 : Only support Java 8 from now on > > [ ] +/- 0 : I don't mind > > [ ] -1 : Keep support for Java 7

Re: Mavibot status?

Fortress core also uses this lib, have just upgraded, release in a couple of weeks. > On Jan 4, 2019, at 5:40 AM, Emmanuel Lécharny wrote: > > Hi Colm, > > I doubt Mavibot is going to be hit by this CVE, but we can upgrade and cut a > release if needed. > > > Give me a bit of time to

Fwd: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Hello, As directed in the message below, we must migrate out four git repos from the existing git-wip-us.apache.org to gitbox.apache.org . Specifically the repos include: directory-fortress-core directory-fortress-realm

Re: Welcome to Lothar !

> > On Dec 19, 2018, at 4:16 PM, Lothar Haeger > wrote: > > I've already managed to link my shiny brand new Apache ID ("lhaeger") to my > GitHub account, so a first question would be: what - if any - are the pros and > cons of using gitbox vs github? Good question. I’ll probably use gitbox,

Re: Exception Running ApacheDS embedded

> On Dec 19, 2018, at 9:39 AM, Emmanuel Lécharny wrote: > > sorry for the delayed response. > > For some reason, ldap-api-all is being loaded while it should not. I have > tried to get rid of it, but it's also present in many dependencies (as a > third party), so it's quite painful. > > One

Re: Exception Running ApacheDS embedded

gt; project. However, even if i missed something in the README, the project > itself is a fully working example that demonstrates how i test my password > policy. It should not be all that difficult to adapt to your use case. Hope > it helps! > > Lucas > > On Fri, Dec 14,

Re: Welcome to Lothar !

Glad to have you onboard Lothar! Shawn > On Dec 17, 2018, at 7:40 AM, Lucas Theisen wrote: > > Welcome Lothar! > > On Mon, Dec 17, 2018, 1:29 AM Kiran Ayyagari Welcome Lothar!, been a while since we last welcomed one :) > > On Mon, Dec 17, 2018 at 11:47 AM Emmanuel Lécharny > wrote: > I'm

Re: Exception Running ApacheDS embedded

ion( resourceName, > resourceDescription ); > } > URL result = resources.nextElement(); > if ( resources.hasMoreElements() ) { > log.debug( "found more than one copy of " + resourceName + " > using first one" ); > } >

Re: [VOTE] - Release Apache Kerby 2.0.0

> On Dec 11, 2018, at 5:49 AM, Colm O hEigeartaigh wrote: > > This is a vote to release Apache Kerby 2.0.0. > +1 Downloaded kerby-all-2.0.0-source-release.zip, validated its signature, built on the OpenJDK Runtime Environment (build 1.8.0_191-b12) / CentOS Linux release 7.5.1804 -- passed

Re: Exception Running ApacheDS embedded

> On Dec 12, 2018, at 5:08 AM, Emmanuel Lécharny wrote: > > if you include ApacheDS, it will implicitely include LDAP API, so including > ldap-api-all will be a duplicate, AFAIR. Here, fortress core apacheDS depends are: test, and of course we have compile-time dependency on the api. > >

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

> On Dec 9, 2018, at 11:08 AM, Stefan Seelmann wrote: > > On 12/9/18 5:37 PM, Shawn McKinney wrote: >> >> In other words, does this change to combine the four into a single git >> project repo force us to also change the structure (and process) of the >

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

> On Dec 8, 2018, at 10:04 AM, Stefan Seelmann wrote: > > If time allows I'd suggest to follow the voluntary relocation. > > For Fortress, if you consider to merge the 4 repos into one, this would > be a good time now. Just create a new "directory-fortress" repo at > Gitbox [1] and merge the 4

Fwd: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

Hello, Currently there are four fortress repos on git-wip-us affected by this change. https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git

[jira] [Commented] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695978#comment-16695978 ] Shawn McKinney commented on FC-258: --- Tested changes, we're good with these changes to core and enmasse

[jira] [Commented] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695974#comment-16695974 ] Shawn McKinney commented on FC-258: --- Here's what I ended up with.      case

[jira] [Created] (FC-259) Fix incorrect setting for bootstrap load script

Shawn McKinney created FC-259: - Summary: Fix incorrect setting for bootstrap load script Key: FC-259 URL: https://issues.apache.org/jira/browse/FC-259 Project: FORTRESS Issue Type: Bug

[jira] [Commented] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692344#comment-16692344 ] Shawn McKinney commented on FC-258: --- Was able to get the tests to run by doing this:     case

[jira] [Commented] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692299#comment-16692299 ] Shawn McKinney commented on FC-258: --- OK, just now testing these changes in the FC-247 branch of enmasse

Re: Caching in Fortress Core

> On Nov 19, 2018, at 6:37 AM, Shawn McKinney wrote: > > Two, its worth outweighs the value. er, costs more than its worth. signature.asc Description: Message signed with OpenPGP

Re: Caching in Fortress Core

> On Nov 16, 2018, at 4:20 PM, Emmanuel Lecharny wrote: > > Persistent search is definitely an option, I think. Fortress will receive all > the updates coming from the LDAP server, and update the cache accordingly. > Now, that may not be that simple: > * consistency: not such a big deal, as

[jira] [Commented] (FC-258) Updating the way FortResponse is served

[ https://issues.apache.org/jira/browse/FC-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689899#comment-16689899 ] Shawn McKinney commented on FC-258: --- Agreed.  What HTTP other status codes need to be mapped from

Fortress' New Logo Usage on Project Website

Hi, Recently a new logo was adopted: https://github.com/apache/directory-fortress-core/blob/master/images/ApacheFortressLogo_FINAL_SM.png Comes in variations, w/out text, size, etc. I’d like to start using this on fortress’ website but want to make sure it’s OK, and hopefully obtain some

Caching in Fortress Core

Many years ago I made a very bad decision that has haunted me ever since — caching. That’s right, short-term gratification (performance) at the expense of long-term satisfaction. The biggest drawback, now things like Fortress REST aren’t running entirely stateless, which prevents running in a

[ANNOUNCE] Apache Fortress 2.0.3 Released

The Apache Directory Project announces its tenth release of Fortress! Apache Fortress is a computer security access management facility written in Java. Other platforms use the Apache Fortress Rest component. Fortress provides a fine-grained authorization security model using role-based access

[VOTE][RESULT] Apache Fortress 2.0.3 release

> I haven't ran the docker test, I haven't installed docker on my (limited) > machine. > > +1 > > On Tue, Nov 6, 2018 at 2:38 PM Shawn McKinney wrote: > >> Hello, >> >> This is an announcement to vote for the next release of Apache Director

[VOTE] Apache Fortress 2.0.3 release

Hello, This is an announcement to vote for the next release of Apache Directory Fortress, 2.0.3. Here are the list of bugs and enhancements: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012315921%20AND%20fixVersion%20%3D%2012344047%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC A

[jira] [Assigned] (FC-256) FORTRESS-REST] Add -version to .war name

[ https://issues.apache.org/jira/browse/FC-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reassigned FC-256: - Assignee: Shawn McKinney Affects Version/s: 2.0.2 Fix Version/s: 2.0.3

[jira] [Resolved] (FC-255) [FORTRESS-WEB] Add -version to .war name

[ https://issues.apache.org/jira/browse/FC-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-255. --- Resolution: Fixed > [FORTRESS-WEB] Add -version to .war n

[jira] [Resolved] (FC-250) Update fortress-rest to Support JSON Data Format

[ https://issues.apache.org/jira/browse/FC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-250. --- Resolution: Fixed > Update fortress-rest to Support JSON Data For

[jira] [Created] (FC-257) Combine the four git repos into one

Shawn McKinney created FC-257: - Summary: Combine the four git repos into one Key: FC-257 URL: https://issues.apache.org/jira/browse/FC-257 Project: FORTRESS Issue Type: Improvement Affects

Re: New Fortress Release 2.0.3

But maybe it's too short term before the actual > release :) > > Kind Regards, > Stefan > > > On 10/26/18 5:29 PM, Shawn McKinney wrote: >> Hello, >> >> This is notification of intent to begin working on a new release of fortress >> 2.0.3, includes enh

[jira] [Resolved] (FC-256) FORTRESS-REST] Add -version to .war name

[ https://issues.apache.org/jira/browse/FC-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-256. --- Resolution: Fixed > FORTRESS-REST] Add -version to .war n

[jira] [Created] (FC-256) FORTRESS-REST] Add -version to .war name

Shawn McKinney created FC-256: - Summary: FORTRESS-REST] Add -version to .war name Key: FC-256 URL: https://issues.apache.org/jira/browse/FC-256 Project: FORTRESS Issue Type: Improvement

[jira] [Created] (FC-255) [FORTRESS-WEB] Add -version to .war name

Shawn McKinney created FC-255: - Summary: [FORTRESS-WEB] Add -version to .war name Key: FC-255 URL: https://issues.apache.org/jira/browse/FC-255 Project: FORTRESS Issue Type: Improvement

[jira] [Resolved] (FC-254) [FORTRESS-WEB] Error Page should not show details

[ https://issues.apache.org/jira/browse/FC-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-254. --- Resolution: Fixed > [FORTRESS-WEB] Error Page should not show deta

[jira] [Created] (FC-254) [FORTRESS-WEB] Error Page should not show details

Shawn McKinney created FC-254: - Summary: [FORTRESS-WEB] Error Page should not show details Key: FC-254 URL: https://issues.apache.org/jira/browse/FC-254 Project: FORTRESS Issue Type: Bug

[jira] [Resolved] (FC-253) [FORTRESS-WEB] Allow startup when fortress.properties not found

[ https://issues.apache.org/jira/browse/FC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-253. --- Resolution: Fixed > [FORTRESS-WEB] Allow startup when fortress.properties not fo

[jira] [Created] (FC-253) [FORTRESS-WEB] Allow startup when fortress.properties not found

Shawn McKinney created FC-253: - Summary: [FORTRESS-WEB] Allow startup when fortress.properties not found Key: FC-253 URL: https://issues.apache.org/jira/browse/FC-253 Project: FORTRESS Issue

New Fortress Release 2.0.3

Hello, This is notification of intent to begin working on a new release of fortress 2.0.3, includes enhancements and bug fixes: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012315921%20AND%20fixVersion%20%3D%2012344047%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC Please let me

[jira] [Resolved] (FC-248) New API to combine createSession & checkAccess

[ https://issues.apache.org/jira/browse/FC-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-248. --- Resolution: Fixed > New API to combine createSession & chec

[jira] [Resolved] (FC-249) New API isUserInRole in AccessMgr

[ https://issues.apache.org/jira/browse/FC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-249. --- Resolution: Fixed > New API isUserInRole in Access

[jira] [Closed] (FC-246) [FORTRESS-CORE] fix NPE in addRoleConstraint when user not assigned to any roles

[ https://issues.apache.org/jira/browse/FC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-246. - > [FORTRESS-CORE] fix NPE in addRoleConstraint when user not assigned to any >

[jira] [Resolved] (FC-245) [FORTRESS-REST] Silently rejects invocations with invalid service name

[ https://issues.apache.org/jira/browse/FC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-245. --- Resolution: Fixed > [FORTRESS-REST] Silently rejects invocations with invalid service n

[jira] [Resolved] (FC-246) [FORTRESS-CORE] fix NPE in addRoleConstraint when user not assigned to any roles

[ https://issues.apache.org/jira/browse/FC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-246. --- Resolution: Fixed > [FORTRESS-CORE] fix NPE in addRoleConstraint when user not assigned to any >

[jira] [Updated] (FC-238) Migrate to LDAP API 2.0

[ https://issues.apache.org/jira/browse/FC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-238: -- Fix Version/s: (was: 2.0.3) 2.0.4 > Migrate to LDAP API

[jira] [Updated] (FC-243) [fortress-realm] proxy to use tomcat 9 interface

[ https://issues.apache.org/jira/browse/FC-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-243: -- Fix Version/s: (was: 2.0.3) 2.0.4 > [fortress-realm] proxy to use tomca

[jira] [Updated] (FC-250) Update fortress-rest to Support JSON Data Format

[ https://issues.apache.org/jira/browse/FC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-250: -- Affects Version/s: 2.0.2 > Update fortress-rest to Support JSON Data For

[jira] [Updated] (FC-250) Update fortress-rest to Support JSON Data Format

[ https://issues.apache.org/jira/browse/FC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-250: -- Fix Version/s: 2.0.3 > Update fortress-rest to Support JSON Data For

[jira] [Updated] (FC-243) [fortress-realm] proxy to use tomcat 9 interface

[ https://issues.apache.org/jira/browse/FC-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney updated FC-243: -- Affects Version/s: 2.0.2 > [fortress-realm] proxy to use tomcat 9 interf

[jira] [Deleted] (FC-251) Support JSON

[ https://issues.apache.org/jira/browse/FC-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney deleted FC-251: -- > Support JSON > > > Key: FC-251 >

[jira] [Resolved] (FC-252) Fix Multitenancy bugs in addRoleConstraint

[ https://issues.apache.org/jira/browse/FC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-252. --- Resolution: Fixed > Fix Multitenancy bugs in addRoleConstra

[jira] [Closed] (FC-252) Fix Multitenancy bugs in addRoleConstraint

[ https://issues.apache.org/jira/browse/FC-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-252. - > Fix Multitenancy bugs in addRoleConstra

[jira] [Created] (FC-252) Fix Multitenancy bugs in addRoleConstraint

Shawn McKinney created FC-252: - Summary: Fix Multitenancy bugs in addRoleConstraint Key: FC-252 URL: https://issues.apache.org/jira/browse/FC-252 Project: FORTRESS Issue Type: Bug Affects

[jira] [Created] (FC-251) Support JSON

Shawn McKinney created FC-251: - Summary: Support JSON Key: FC-251 URL: https://issues.apache.org/jira/browse/FC-251 Project: FORTRESS Issue Type: Improvement Affects Versions: 2.0.2

[jira] [Created] (FC-249) New API isUserInRole in AccessMgr

Shawn McKinney created FC-249: - Summary: New API isUserInRole in AccessMgr Key: FC-249 URL: https://issues.apache.org/jira/browse/FC-249 Project: FORTRESS Issue Type: Improvement Affects

[jira] [Created] (FC-248) New API to combine createSession & checkAccess

Shawn McKinney created FC-248: - Summary: New API to combine createSession & checkAccess Key: FC-248 URL: https://issues.apache.org/jira/browse/FC-248 Project: FORTRESS Issue Type: Improve

[jira] [Reopened] (FC-245) [FORTRESS-REST] Silently rejects invocations with invalid service name

[ https://issues.apache.org/jira/browse/FC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reopened FC-245: --- also silently rejects other requests that have uncaught exceptions, e.g. class cast or NPE's.  Change Fault

Re: rm -rf *Decorator ;-)

> On Oct 3, 2018, at 9:12 AM, Emmanuel Lécharny wrote: > > The problem is that the implementation was really a nightmare (and still > is). Anyone who wants to add a new extendedOperation or a nex Control > has to go through many classes and is likely to get lost (I experienced > it last month

[jira] [Created] (FC-246) [FORTRESS-CORE] fix NPE in addRoleConstraint when user not assigned to any roles

Shawn McKinney created FC-246: - Summary: [FORTRESS-CORE] fix NPE in addRoleConstraint when user not assigned to any roles Key: FC-246 URL: https://issues.apache.org/jira/browse/FC-246 Project: FORTRESS

[jira] [Resolved] (FC-245) [FORTRESS-REST] Silently rejects invocations with invalid service name

[ https://issues.apache.org/jira/browse/FC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-245. --- Resolution: Fixed Place a default service to return an error in the response and place a warning

[jira] [Created] (FC-245) [FORTRESS-REST] Silently rejects invocations with invalid service name

Shawn McKinney created FC-245: - Summary: [FORTRESS-REST] Silently rejects invocations with invalid service name Key: FC-245 URL: https://issues.apache.org/jira/browse/FC-245 Project: FORTRESS

Re: Anyone going to ApacheCon in Montreal?

> On Sep 14, 2018, at 7:24 AM, Moyer, Steven William wrote: > > I won't be in Montreal but I'm thinking about proposing a talk at the > ApacheCon Roadshow in DC ... is anyone else planning to talk about > identity-related subjects there? > Haven’t got that far into the future yet Steve.

Re: Anyone going to ApacheCon in Montreal?

> On Sep 14, 2018, at 3:59 AM, Pierre Smits wrote: > > Unfortunately I can't justify the projected cost against the implied > benefits, so I won't be there (though I pity that much). > > But there are talks that in 2019 there might be an ApacheCon EU event. I am > hoping that will

Re: Anyone going to ApacheCon in Montreal?

> On Sep 13, 2018, at 6:04 AM, Colm O hEigeartaigh wrote: > > > Yes I'll be there as well - hope to see you there! Great! I saw that you’re speaking on Thursday. Pity that I’m leaving on that day. Looks like an interesting talk, hope it’s recorded. Will see you there... —Shawn

[ANNOUNCE] Apache Fortress 2.0.2 Released

The Apache Directory Project announces the ninth release of Fortress — 2.0.2. Apache Fortress is a computer security access management facility written in Java. Other platforms use the Apache Fortress Rest component. Fortress provides a fine-grained authorization security model using

<    1   2   3   4   5   6   7   8   9   10   >