The Fortress Commander UI and Java API provide mechanisms to set and retrieve
temporal constraints on a role. Is there any way to add additional arbitrary
constraints that are not time related? For example, a bank teller can only work
with a certain set of accounts.
Thanks,
~Chris Pike
validator, but how can I
pass my arbitrary input to check access?
~Chris Pike
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Monday, August 24, 2015 11:17:18 AM
Subject: Re: [Bulk] RBAC Constraints
> On Aug 24, 2015, at 8:14 AM, Shawn Mc
Is there a recommended way to contribute code changes (new functionality or bug
fixes) back to the fortress project?
I have seen other Apache projects have a mirrored project on Github, which
allows creating Github pull requests.
~Chris Pike
e.org
Sent: Monday, August 31, 2015 7:28:50 PM
Subject: Re: Contributing Code Changes
Le 31/08/15 14:38, Chris Pike a écrit :
> Is there a recommended way to contribute code changes (new functionality or
> bug fixes) back to the fortress project?
The best way to do it is to attach a diff o
I have noticed that when I make changes to roles, I often have to reassign the
user to get the updates to be reflected in the API calls. How often is the
cached data updated and is there a way to force an update?
Given the following scenario... I have 1000's of roles in my system and an
ARBAC role that has a narrow role range defined. I want to show a admin user in
that ARBAC role what roles they can assign to a user.
Is there any current API calls that provide that capability? The review manager
findR
RBAC roles are assigned to ARBAC roles through role ranges (a starting child
node and an ending parent node). This range determines the set of roles that a
user in the Admin Role can assign users. Given a complex RBAC role hierarchy or
many roles not part of a hierarchy, this would require many
docker can be run on windows, ansible can not run on windows as a control
machine. Is running on windows a goal of the project? (could still be done,
would just be more manual process) Thoughts on this approach?
Thanks,
~Chris Pike
rtress Build Process / Quickstarts
> On Nov 19, 2015, at 9:27 AM, Chris Pike wrote:
>
>
> I have been looking at the fortress build process and install scripts. In the
> past, we have built ansible roles
> (https://github.com/PennState/fortress-in-a-box), but they still rely on th
How would you handle giving roles/permissions to all authenticated or anonymous
users in fortress?
: fortress@directory.apache.org
Sent: Tuesday, December 8, 2015 9:30:39 AM
Subject: Re: All or Anonymous User Roles
>
> On Dec 8, 2015, at 7:41 AM, Chris Pike wrote:
>
> How would you handle giving roles/permissions to all authenticated or
> anonymous users in fortress?
The tricky part
For anyone interested,
I updated the psu fortress-in-a-box project which has ansible scripts to
install fortress with either openldap or apacheds. It also has files to create
separate docker images and use them together with a provided.
docker-compose.yml file.
https://github.com/PennState/for
directory.apache.org
Sent: Tuesday, December 8, 2015 11:41:41 AM
Subject: Re: All or Anonymous User Roles
> On Dec 8, 2015, at 9:26 AM, Chris Pike wrote:
>
> Currently, our clients use the fortress API to lookup roles and permissions
> for the already authenticated user. So being authen
I think there are a few options...
1. Docker - Goal here is to build the docker images and use docker-compose to
run them (see instructions at bottom of README). Yes, need to install docker
first (don't have to do this on a VM). If running windows or mac, additionally
need docker-machine, this
that could be done
without breaking or at least extending RBAC.
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Tuesday, December 8, 2015 1:23:39 PM
Subject: Re: All or Anonymous User Roles
> On Dec 8, 2015, at 11:53 AM, Chris Pike wrote:
We had discussed the idea of a RoleOU, similar to a PermOU, which would be used
by ARBAC and eliminate the ARBAC role explosion problem. It would also give us
an easy way to group roles for a particular application together. What are your
thoughts on that proposal?
- Original Message -
Assuming I understand what your saying, that sounds great.
So they would be similar to the current Temporal Constraints, but really just
check boxes, one for Anon and another for Auth. So when a session was activated
for an authed user, any roles (and therefore permissions) with the
isAuthentic
Is there an API call get all permissions assigned to a role that doesn't look
at the role hierarchy?
The ReviewManager "rolePermissions" method returns all permissions granted or
inherited, but I need a method that only returns permissions directly assigned
to the role.
?
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Monday, December 14, 2015 12:19:36 PM
Subject: Re: Retrieving Role Permissions
> On Dec 14, 2015, at 10:00 AM, Chris Pike wrote:
>
> Is there an API call get all permissions assigned to a rol
December 14, 2015 3:01:10 PM
Subject: Re: Retrieving Role Permissions
> On Dec 14, 2015, at 12:44 PM, Chris Pike wrote:
>
>
> On the review manager, there is a method permissionUsers that says it returns
> all users who have been directly granted a permission. How can a user be
&g
github.com/apache/directory-fortress-core/pull/2
Let me know what you think
- Original Message -----
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Tuesday, December 15, 2015 11:39:55 AM
Subject: Re: Retrieving Role Permissions
Ok, another API question, I&#x
There are a couple instances where models have multiple set methods for the
same field.
UserAdminRole has...
public void setOsP( String osP )
public void setOsP( Set osPs )
public void setOsU( Set osUs )
public void setOsU( String osU )
User has...
public void setRole( St
I made the change and submitted a pull request on github, however I got an
error when trying to run the junit tests. I reverted the code and still get the
same error when running the test so it is not an issue with something I
changed. I put the error in the github comment.
- Original Mess
Adding the disable.audit=false didn't fix the issue. Does it matter if I'm
using openldap or apacheds?
- Original Message -----
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Wednesday, January 6, 2016 10:18:33 AM
Subject: Re: Multiple Set Methods on Mo
6, at 9:32 AM, Chris Pike wrote:
>
> Adding the disable.audit=false didn't fix the issue. Does it matter if I'm
> using openldap or apacheds?
Yes it does. If you are using apachds add this flag:
ldap.server.type=apacheds
For openldap this one:
ldap.server.type=openldap
When
For openldap there is a fortress.schema and rbac.schema. What is the
rbac.schema and where/how is it being used?
ss of
how I change the build.properties, the same 5 tests always fail.
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Friday, January 8, 2016 12:31:29 PM
Subject: Re: Multiple Set Methods on Models
> On Jan 6, 2016, at 7:33 AM, Chris P
We want to be able to store attributes/constraints in fortress so that we can
do fine grained security checks. We would like to get thoughts/feedback on this
proposal. Our goal is to store permission attributes and role constraints based
on those attribute in fortress, but not necessarily have f
ress@directory.apache.org
Sent: Thursday, January 14, 2016 1:09:24 PM
Subject: Re: Fortress Constraints
> On Jan 14, 2016, at 10:07 AM, Chris Pike wrote:
>
> We want to be able to store attributes/constraints in fortress so that we can
> do fine grained security checks. We would lik
possible. Our runtime complexity target should be
O(log N). That means we’ll need to find an efficient way to join without
(much) looping. We’ll also need to ensure the complexity doesn’t leak into
areas where the attribute feature isn’t used / needed.
Shawn
> On Jan 17, 2016, at 7:04 AM,
52:22 AM
Subject: Re: Fortress Constraints
> On Jan 27, 2016, at 3:17 PM, Chris Pike wrote:
>
> started implementing this and one of the things I am concerned with is
> duplicate ftPA entries. Most of our permissions will likely share the same
> attribute(s), so the f
String attributeSet;
- Any unloading of a permission would read the ftPA entry and populate this
field
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Thursday, January 28, 2016 10:01:54 AM
Subject: Re: Fortress Constraints
> On
nce of events during usage?
For example:
1. createSession does these ops:
a. readUser
b. bind
2. sessionPermissions
a. searchPermissions
what changes within these sequences?
No changes to accessmgr other than these two methods?
Shawn
> On Jan 28, 2016, at 9:29 AM, Chris Pike wrote:
>
l Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Thursday, January 28, 2016 10:01:54 AM
Subject: Re: Fortress Constraints
> On Jan 28, 2016, at 8:50 AM, Chris Pike wrote:
>
> Every application could define several permission attributes, and since we
rivate String attributeSet;
- Any unloading of a permission would read the ftPA entry and populate this
field
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Thursday, January 28, 2016 10:01:54 AM
Subject: Re: Fortress Constraints
&
Shawn,
1. You need to clone the repo, then checkout the branch you want, so
git clone https://github.com/PennState/directory-fortress-core-1.git
git checkout feature/addPermAttrAndUserRoleConstraints
2. The audit tests still fail in my environment, I'll look through your updated
documentation,
mmary =500 in 8.3s = 60.4/s Avg:10 Min: 2 Max:
104 Err: 0 (0.00%)
Error after runs
[info] The JVM should have exitted but did not.
[info] The following non-daemon threads are still running (DestroyJavaVM is OK):
...
~Chris
- Original Message -
From: "Chris
Is there any documentation or code examples on how to use the session with the
API. I've been experimenting with ARBAC roles, for example, assigning user to a
role
adminManager.assignUser(new UserRole("testUser", "testRole"));
I have an ARBAC role setup to allow this, but the only way I can ac
It is my understanding that anyone in an ARBAC role with the permission
org.apache.directory.fortress.core.impl.DelAdminMgrImpl.assignUser can assign
any user to any ARBAC role. Is that correct?
I don't see any ARBAC permissions for the access manager. Is there any way to
restrict who can call the access managers methods (authorizedRoles,
sessionRoles, etc...)?
d with their
application.
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Monday, February 8, 2016 1:51:36 PM
Subject: Re: ARBAC Role Assignment Question
> On Feb 8, 2016, at 10:08 AM, Chris Pike wrote:
>
> It is my understanding that
ermissions
> On Feb 8, 2016, at 12:33 PM, Chris Pike wrote:
>
> I don't see any ARBAC permissions for the access manager. Is there any way to
> restrict who can call the access managers methods (authorizedRoles,
> sessionRoles, etc...)?
No. It could be added, just nev
y.apache.org
Sent: Monday, February 1, 2016 1:12:02 PM
Subject: Re: Fortress Constraints
> On Jan 31, 2016, at 12:01 PM, Chris Pike wrote:
>
>
> 1. You need to clone the repo, then checkout the branch you want, so
>
> git clone https://github.com/PennState
rg
Sent: Tuesday, February 9, 2016 12:23:45 PM
Subject: Re: Fortress Constraints
> On Feb 9, 2016, at 9:52 AM, Chris Pike wrote:
>
>
> Looks like I'm running Symas OpenLDAP 2.4.42. There are lots of audit logs
> being populated in openldap, so probably not a configuration
y 8, 2016 5:27:17 PM
Subject: Re: Access Manager Permissions
> On Feb 8, 2016, at 4:08 PM, Chris Pike wrote:
>
> We have a REST service that will get called to retrieve the active roles for
> a user. Need to restrict who can make this call.
How is that user credential being passed
Shawn,
We are using the fortress model classes in our projects, but including the
directory-fortress-core dependencies in our pom brings along a lot of extra
dependencies, some of which are causing issues in some of our projects. Would
you be amenable to some changes in the directory-fortress-c
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Monday, February 15, 2016 10:56:33 AM
Subject: Re: Directory Fortress Core Dependencies
> On Feb 15, 2016, at 9:05 AM, Chris Pike wrote:
>
> We are using the fortress model classes in our projects, but including t
: fortress@directory.apache.org
Sent: Tuesday, February 9, 2016 5:17:35 PM
Subject: Re: Access Manager Permissions
> On Feb 9, 2016, at 3:36 PM, Chris Pike wrote:
>
> Using oauth bearer token in HTTP header to determine user. How would the the
> policy work, just do a check to
ions
> On Feb 19, 2016, at 10:03 AM, Chris Pike wrote:
>
> So, what exactly would need modified?
>
> 1. Create admin objects and permissions in ldap
> 2. Add a method to access manager to set the admin session
> 3. Add setEntitySession methods into the access manager meth
- Original Message -----
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Friday, February 19, 2016 2:27:11 PM
Subject: Re: Access Manager Permissions
I work on getting the last 2 tests to pass, think
- Original Message -
From: "Shawn McKinney"
To: fort
19, 2016 2:55:32 PM
Subject: Re: Access Manager Permissions
> On Feb 19, 2016, at 1:39 PM, Chris Pike wrote:
>
> Still think there are two tests that are failing, I'll see about getting it
> working then commit directly.
>
> Here is the slapd.conf I'm currently using if s
I just ran the tests a second time and they all passed, so appears to only fail
on first run through.
- Original Message -
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Saturday, February 20, 2016 8:43:05 AM
Subject: Re: Access Manager Permissions
Down to one f
We have a REST service that uses the fortress API and deploys to a wildfly
application server. If the service is processing lots of requests when we
redeploy the application, it causes the application server to hang and we have
to restart.
Not sure what the problem is but think it might be rela
I've been playing around with closing the connection pools... I added this into
ApacheDsDataProvider and call it when the war shuts down, however it doesn't
solve the problem. Is this the correct location and way to close the pools?
public static void closeAllConnectionPools(){
try {
ative number after, so not sure what to make of that.
- Original Message -
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Friday, March 4, 2016 11:06:28 AM
Subject: Re: LDAP Connection Management
I've been playing around with closing the connection pools.
LDAP Connection Management
Le 04/03/16 21:10, Chris Pike a écrit :
> Some more information
>
> I setup my service to periodically print the admin pools active and idle
> connections. The hang problem happens after a successful redeploy, but the
> web server stops processing reques
g the lock?
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Sunday, March 6, 2016 10:17:35 AM
Subject: Re: LDAP Connection Management
> On Mar 6, 2016, at 8:03 AM, Chris Pike wrote:
>
> After a lot of troubleshooting, I'm not
inney"
To: fortress@directory.apache.org
Sent: Sunday, March 6, 2016 2:37:54 PM
Subject: Re: LDAP Connection Management
> On Mar 6, 2016, at 1:08 PM, Chris Pike wrote:
>
> I'm not an expert on concurrency, but I think the problem might be the code
> trying to upgrade the read l
I'm guess I'm not following why the original code wasn't working. Ehcache is
thread safe.
- Original Message -
From: "Emmanuel Lécharny"
To: fortress@directory.apache.org
Sent: Sunday, March 6, 2016 3:28:07 PM
Subject: Re: LDAP Connection Management
Le 06/
P Connection Management
Le 06/03/16 23:50, Shawn McKinney a écrit :
>> On Mar 6, 2016, at 3:52 PM, Chris Pike wrote:
>>
>> I'm guess I'm not following why the original code wasn't working. Ehcache is
>> thread safe.
> True, but that thread safety doesn’t cov
harny"
To: fortress@directory.apache.org
Sent: Monday, March 7, 2016 1:40:50 AM
Subject: Re: LDAP Connection Management
Le 07/03/16 03:36, Chris Pike a écrit :
> So I changed it to this locally...
>
> String key = getKey( contextId );
>
> LOG.in
ement
Le 07/03/16 14:28, Chris Pike a écrit :
> Sorry, trying to understand... in your example, if the second thread gets
> null and calls loadGraph a second time, what problem does that cause (other
> than loading data twice)? Asked another way, what about loadGraph is not
> thread
I tried implementing the suggested code, and while it works in eclipse, when
running the service, the first run passes, but all subsequent requests hang
while getting object from the cache.
After looking more closely at the caching code, it is already using a blocking
cache, which by default wi
lt in
simultaneous loadGraph calls, so I also made the loadGraph method synchronized.
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Wednesday, March 9, 2016 10:33:45 AM
Subject: Re: LDAP Connection Management
> On Mar 8, 2016, at 2:08 PM, Chris P
Yes, I'll commit the changes later today, I already updated those others
classes and AdminRoleUtil as well.
I fine with waiting for next release, we are using our own release branch for
internal deployments.
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.
Changes are committed
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Wednesday, March 9, 2016 12:15:13 PM
Subject: Re: LDAP Connection Management
> On Mar 9, 2016, at 11:08 AM, Chris Pike wrote:
>
> Yes, I'll commit th
and getPolicySet).
Since these are both also using a blocking cache, I think the locking is
unnecessary.
- Original Message -
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Wednesday, March 9, 2016 3:22:15 PM
Subject: Re: LDAP Connection Management
Changes are
bject: Re: LDAP Connection Management
> On Mar 11, 2016, at 10:11 AM, Chris Pike wrote:
>
> Found another place wehre this might be an issue...
>
> OrgUnitP and PolicyP both use read locks in the isValid method and write
> locks in the add method, but only around getting user and
We need to handle the config initialization differently. See the static init
block in this class...
https://github.com/apache/directory-fortress-core/blob/master/src/main/java/org/apache/directory/fortress/core/util/Config.java
If this fails when the application starts, it throws an exception an
Shawn,
I'm new to the process and I think it would help if you provided a basic
overview... Who is allowed vote, how does someone vote, what happens when a
vote is passed, what is expected of someone who votes yes, etc...?
Thanks,
~Chris
- Original Message -
From: "Shawn McKinney"
ubject: Re: Static Config Initialization Problems
> On Mar 11, 2016, at 7:01 PM, Chris Pike wrote:
>
> We need to handle the config initialization differently. See the static init
> block in this class...
>
> https://github.com/apache/directory-fortress-core/blob/master/src/m
ers List"
Sent: Saturday, March 12, 2016 8:41:55 AM
Subject: Re: [VOTE] Release Apache Directory Fortress 1.0-RC42
> On Mar 12, 2016, at 7:20 AM, Chris Pike wrote:
>
> I'm new to the process and I think it would help if you provided a basic
> overview... Who is allowed vote
inney"
To: fortress@directory.apache.org
Sent: Tuesday, March 15, 2016 12:24:51 PM
Subject: Re: Static Config Initialization Problems
Apologize for delay responding, am traveling atm….
> On Mar 12, 2016, at 7:41 AM, Chris Pike wrote:
>
> Yes, the actual problem is that fortress can&#
first and not
call it in a static context.
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Tuesday, March 15, 2016 4:58:16 PM
Subject: Re: Static Config Initialization Problems
> On Mar 15, 2016, at 3:38 PM, Chris Pike wrote:
>
>
1. Don't need to code retry logic. If getInstance() throws exception, INSTANCE
will still be null so next call will just try again.
2/3. This will depend on the situation. In most cases, I think we can simply
remove the static variable and put a method call to
Confg.getInstance().getProperty in
atedMethodAccessor911.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
- Original Message -----
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Friday, March 11, 2016 12:19:21 PM
Subject: Re: LDAP Con
apache.org
Sent: Monday, March 21, 2016 12:26:01 PM
Subject: Re: LDAP Connection Management
Le 21/03/16 17:18, Chris Pike a écrit :
> This problem reared it's ugly head again... fortunately, we were able to get
> a thread dump and it looks like it is an issue with the ldap api connect
Having a method name field / arbac permission that doesn't match the actual
method name is confusing. What about changing the method to
findPermissionsByPermObj?
- Original Message -
From: "Shawn McKinney"
To: fortress@directory.apache.org
Sent: Monday, March 21, 2016 10:48:59 PM
Subje
;
To: fortress@directory.apache.org
Sent: Monday, March 21, 2016 11:06:41 PM
Subject: Re: LDAP Connection Management
> On Mar 21, 2016, at 12:52 PM, Emmanuel Lécharny wrote:
>
> Le 21/03/16 18:20, Chris Pike a écrit :
>> Why isn't it being closed? Will setting the timeout on the connection
: Re: LDAP Connection Management
> On Mar 22, 2016, at 7:30 AM, Chris Pike wrote:
>
> Yes, I saw that as well. My next step was going to be to create a fortress
> config property to set set it. However, looking through the code in the
> thread dump, I wasn't certain setting it wo
I've done lots of testing with redeploying while running jmeter tests, that's
how I discovered the previous thread locking issues. I just haven't been able
to reproduce this error in my local test environment.
The thread dumps all show that the errors are on validating the connection
while borr
etTimeout method
- Original Message -
From: "Emmanuel Lécharny"
To: fortress@directory.apache.org
Sent: Wednesday, March 23, 2016 11:54:26 AM
Subject: Re: LDAP Connection Management
Le 22/03/16 21:27, Chris Pike a écrit :
> I've done lots of testing with redeploying
ok, how do I get this code into my environment? Does the ldap api have a git
mirror?
- Original Message -
From: "Emmanuel Lécharny"
To: fortress@directory.apache.org
Sent: Wednesday, March 23, 2016 12:48:38 PM
Subject: Re: LDAP Connection Management
Le 23/03/16 17:24, Ch
t
> On Mar 24, 2016, at 4:16 AM, Emmanuel Lécharny wrote:
>
> Le 23/03/16 19:30, Chris Pike a écrit :
>> ok, how do I get this code into my environment? Does the ldap api have a git
>> mirror?
> Nope. This is still using Subversion.
>
> Youc an check out the code
Are we going to add this fix (setTestWhileIdle and
setTimeBetweenEvictionRunsMillis) into the source?
- Original Message -
From: "Jan Sindberg"
To: fortress@directory.apache.org
Sent: Friday, February 12, 2016 3:52:17 PM
Subject: Re: LDAP connection timeout
>
>
> Every 30 minutes this
We are using OpenLDAP, but adding the lines into our code seems to have fixed a
few infrequent timeout errors. I don't understand the intracacies of the
connections and the pooling, but it is probably worth waiting until the ldap
api updates to the newer version of commons pool before spending a
+1
Rebuilt VM with 1.0.0 tag and OpenLDAP and ran junit tests
- Original Message -
From: "Shawn McKinney"
To: "Apache Directory Developers List"
Cc: fortress@directory.apache.org
Sent: Tuesday, April 12, 2016 11:06:25 AM
Subject: [VOTE] Release Apache Directory Fortress 1.0.0
Once aga
Jiajia,
Did you verify tomcat is running and you can login with credentials in Section
5, Step 9?
Do the tomcat logs show any errors?
- Original Message -
From: "Li, Jiajia"
To: "Apache Directory Developers List"
Cc: fortress@directory.apache.org
Sent: Thursday, April 14, 2016 4:33
When creating a user using the fortress API, a userPassword field is created,
even though I'm not specifying one for the user. What value is being put here?
Is there a way to disable it's creation?
: Static Config Initialization Problems
> On Mar 16, 2016, at 10:52 AM, Chris Pike wrote:
>
> 1. Don't need to code retry logic. If getInstance() throws exception,
> INSTANCE will still be null so next call will just try again.
OK
>
> On Mar 16, 2016, at 10:52 AM,
: fortress@directory.apache.org
Sent: Sunday, April 17, 2016 10:21:37 PM
Subject: Re: Static Config Initialization Problems
> On Apr 17, 2016, at 5:46 PM, Chris Pike wrote:
>
> I'd like to make these changes soon, but want to make sure you are still OK
> with the proposed changes before I
zation Problems
> On Apr 18, 2016, at 7:07 AM, Chris Pike wrote:
>
> Here is the how the config class would be changed.
>
> https://github.com/PennState/directory-fortress-core-1/blob/feature/modifyBootstrapSingleton/src/main/java/org/apache/directory/fortress/core/util/Config
: Static Config Initialization Problems
> On Apr 19, 2016, at 7:34 AM, Chris Pike wrote:
>
> Ok, I'll work on my branch and get the tests working. What do you mean by
> wrap Config.getInstance() with CONFIG?
Cool.
Please use a method wrapper such as this for the code reference
ubject: Re: User Password Field
> On Apr 14, 2016, at 7:46 AM, Chris Pike wrote:
>
> When creating a user using the fortress API, a userPassword field is created,
> even though I'm not specifying one for the user. What value is being put
> here? Is there a way to disable i
word Field
> On Apr 21, 2016, at 2:18 PM, Chris Pike wrote:
>
> Any objection if I modify the code to allow not setting the user password
> field via a property? Something like
>
> user.creation.field.password.disable=true
Go ahead. I will need to make sure it doesn’t break
, April 21, 2016 6:21:41 PM
Subject: Re: User Password Field
> On Apr 21, 2016, at 3:29 PM, Chris Pike wrote:
>
> Ok, I created an issue and will make the change. Is there a documentation
> page anywhere for all the different fortress properties?
Other than on the entity class itself? No.
19, 2016, at 10:18 AM, Chris Pike wrote:
>
> We can't use a static variable since it would result in the same problem we
> are trying to fix (exceptions on static initialization)
ah crap you’re right.
6, 2016 4:02:34 PM
Subject: Re: Static Config Initialization Problems
> On Apr 26, 2016, at 2:26 PM, Chris Pike wrote:
>
>
> I went ahead and refactored to not use static init blocks. There was a huge
> ripple effect through the code and I ran into some other problems along the
Yeah, looks like running from the command line is causing infinite loop. Is the
command line "mvn -Dtest=FortressJUnitTest test" still using ant?
- Original Message -----
From: "Chris Pike"
To: fortress@directory.apache.org
Sent: Tuesday, April 26, 2016 4:16:15 PM
onfig Initialization Problems
Negative.
Original message From: Chris Pike
Date:04/26/2016 3:32 PM (GMT-06:00)
To: fortress@directory.apache.org Subject: Re: Static
Config Initialization Problems
Yeah, looks like running from the command line is causing infinite loop.
Is t
1 - 100 of 185 matches
Mail list logo
