[JBoss JIRA] Created: (GTNPORTAL-2119) Typo in UIPortalNavigation.gtmpl
by Marek Posolda (JIRA)
Typo in UIPortalNavigation.gtmpl
--------------------------------
Key: GTNPORTAL-2119
URL: https://issues.jboss.org/browse/GTNPORTAL-2119
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: WebUI
Affects Versions: 3.2.0-M01
Reporter: Marek Posolda
Priority: Minor
Fix For: 3.2.0-M02
Attachments: exception-classCastException.txt
It's small typo in template UIPortalNavigation.gtmpl . It references to bad type "Node" when it should be "UserNode" . Can be fixed on this line:
- for(Node node in childs) {
+ for(UserNode node in childs) {
It's working "by accident" even if there is wrong type declared now, but when I tried to upgrade groovy to 1.8.2 it throws me ClassCastException because of this (see stacktrace in attachement)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (GTNPORTAL-1926) DB and LDAP in read-only: user attributes are saved only to DB but they are still read from LDAP
by Marek Posolda (JIRA)
DB and LDAP in read-only: user attributes are saved only to DB but they are still read from LDAP
------------------------------------------------------------------------------------------------
Key: GTNPORTAL-1926
URL: https://issues.jboss.org/browse/GTNPORTAL-1926
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Identity integration
Affects Versions: 3.1.0-GA
Environment: - EPP 5.1.1.DEV01 with latest exo.portal.component.identity from GateIn trunk
- Picketlink 1.3.0.Alpha03
- LDAP configured with read-only setup (picketlink-idm-ldap-acme-config.xml from "example" folder used as configuration file)
Reporter: Marek Posolda
Assignee: Boleslaw Dawidowicz
Fix For: 3.2.0-GA
I have LDAP configured as read-only (Parameter "readOnly" with value "true" is configured as option in configuration of "PortalRepository" in picketlink configuration file picketlink-idm-ldap-acme-config.xml )
And then I am doing this in EPP UI:
1) Login as "mposolda" with password
2) Click to my name in right top corner
3) Change my first name and last name to "Marekkk Poosoldaaaa".
4) Click "Save" and I have message that attributes are changed successfully
5) Logout
6) Login again as mposolda
7) I am seeing that I am still "Marek Posolda"
Problem is that attributes are written to DB in method FallbackIdentityStoreImpl.updateAttributes (which is correct) but then they are read from LDAP in FallbackIdentityStoreImpl.getAttributes and DB attributes are simply ignored . This is confusing for users, because they may have feeling that their attributes are updated but they aren't)
I think that one of these two conditions should be met:
a) Show warning in step 4 that user can't change LDAP attributes (like FirstName, Lastname or Email)
b) Don't show warning but in this case, attributes from DB should have preference over attributes from LDAP.
It will be nice if this can be configurable and administrator can choose between option (a) or (b)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (GTNPORTAL-1763) can't logout after authentication with CAS server
by houssem njah (JIRA)
can't logout after authentication with CAS server
-------------------------------------------------
Key: GTNPORTAL-1763
URL: https://issues.jboss.org/browse/GTNPORTAL-1763
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.1.0-GA
Environment: tomcat package
Reporter: houssem njah
Hi,
after login with CAS server, i can't logout from portal
in fact:
-i click on link "logout"
- i get screen from CAS server that told me that i'm realy logger out.
- if i go to this url /portal:public/classic, i see that i still logged in to the portal
in the normal result, i must see the portal as a guest user (not logged in yet)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] Created: (GTNMGMT-13) Support PUT, POST, and DELETE http methods for management requests.
by Nick Scavelli (JIRA)
Support PUT, POST, and DELETE http methods for management requests.
-------------------------------------------------------------------
Key: GTNMGMT-13
URL: https://issues.jboss.org/browse/GTNMGMT-13
Project: GateIn Management
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: rest
Reporter: Nick Scavelli
Assignee: Nick Scavelli
Supporting POST, PUT, and DELETE means mapping these requests to management operations, add-resource, update-resource, and remove-resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years