[Athen] authorization conflict between JFW and WYNN

[James Bailey]

I have discovered what may be a conflict between WYNN 4.0 and JFW 7.0
authorization schemes.  I tried to install a single user version of WYNN
4.0 on a machine that has JFW 7.0 on it.  The JFW get its authorization
from a server.  In every other respect this JFW is handled as a local
set-up, it just gets authorization from a server.

I could not successfully "activate" the WYNN set-up.  When one of the WYNN
error messages mentioned the JFW authorization server by name, I became
highly suspicious.  Three separate calls to FS help got the same response,
"the two authorizations schemes will ignore each other."

Finally, I commented out the JFW authorization by changing the name of the
environmental variable, and (you know what's coming) WYNN started up just
fine.  Of course now JFW starts in the demo mode not being able to access
the authorization.

Has anyone else encountered and resolved this issue?

- Thanks, James

James Bailey
Adaptive Technology Access Adviser, University of Oregon
1299 University of Oregon
Eugene, OR 97403-1299
Office: 541-346-1076
jbailey at darkwing.uoregon.edu