This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Currently, the Servers node in the Services tab contains action "Identity Usage...", which activates the identity modules. This action was introduced as a fix/workaround for issue 158765. Basically, under the rules of Ergonomics, you could no longer follow the steps described in this document: http://www.netbeans.org/kb/60/javaee/identity-amsecurity.html In particular, step 10 in the "installing..." section only works if the Identity modules are enabled: "The Sun Java System Access Manager appears as a node in the Services Tab under the Application Server you have just installed. You must start the Application Server to begin working with Sun Java System Access Manager." A better solution would be if the GF plugin detected if the Access Manager is installed, and if it is, displayed the AM node, even if the Identity modules are not enabled. When the user starts working with the node, the Identity modules would be automagically enabled. This would obviate the need for the "Identity usage" action, which is an extra manual steps needed if Identity features are desired. BTW, what would be a better name for the "Identity" feature, that could be displayed in the Plugins dialog? Any ideas? Maybe "Access Manager"?
do we need to worry about AM on remote servers? Why doesn't identity just get activated when the gf v2 plugin gets activated? Isn't that an easier solution?
That's also a possibility. The downside is that the users who don't have AM installed (which is the majority) would have to pay the penalty of having the Identity modules installed, on the other hand, this is 5 modules, so this penalty is probably not high. To do this, we would probably need to kill the 'identity' cluster and just move the modules to the 'enterprise' cluster.
As for name of feature - "Access Manager" is only a Glassfish tool,whereas whole functionality is named "Identity Support" and contains not only AM support,but also support for Web and J2EE projects, so I vote for leaving Identity as name. About AM on remote servers - yes,this was part of original intent and this feature should work,but so far I didn't met any user,using this nor seen any mail supporting it. As for automatic activation "Identity" along with installation of Glassfish v2, that's questionable,since there was always only Java Application Platform SDK Glassfish Identity support,and on any other server Identity isn't supported,tested and can occur issues. I mean in first place variant of bundled Glassfish,with AM added from Update Center, which was rejected from support. On other hand,we can highlight to user neccessity of use supported version of Glassfish in tutorials,so this problem could be avoided.
Another possibility would be if the GF plugin "recommends" the identity modules. This way, after enabling the Java EE features, Identity would also be enabled, but it would stay separate, and it would be possible to turn it off without turning off Java WebApps. Also, currently the Identity modules are displayed with the coarse view (when "Advanced view" is unchecked), and it probably should not be there as it's too specific. This change would allow us to exclude it from this view, am I right? As for the name, Jarda Pospisil and I talked offline and we suggest "Identity Management". I am attaching a patch for these changes.
Created attachment 80658 [details] Patch for the changes above
The changes to j2ee.sun.appsrv81 look fine to me. I cannot speak to the other changes.
Ok, I pushed the changes. http://hg.netbeans.org/web-main/rev/af00915204b1 Jardo, so is it possible to now hide the Identity Usage... action? Thanks.
Integrated into 'main-golden', will be available in build *200904230201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/af00915204b1 User: pjiricka@netbeans.org Log: #162979 (preparation) - making GlassFish plugin recomment Identity so it gets enabled when WebApps are enabled, and tweaking the display name.
core-main#6f5b31fc28be
Integrated into 'main-golden', will be available in build *200908110201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/6f5b31fc28be User: Jaroslav Tulach <jtulach@netbeans.org> Log: #162979: Don't display Identity Usage action