The embedded CAS server does not log to a file in the 4.0.x line since 2010. It does in master since 9/26/2012 when I made systemic logging changes to use environment variables in the overlay log files.
Anyone have concerns with having the 4.0.x line embedded cas log into cas.log like 4.1? It shouldn't be a security issue AFAIK. Thanks, James Wennmacher - Unicon 480.558.2420 -------- Original Message -------- Subject: Re: [uportal-user] jasig cas secure connection Date: Fri, 11 Apr 2014 10:21:55 -0700 From: James Wennmacher <[email protected]> To: [email protected] That's interesting. For some reason the 4.0.x branch has a null appender in the cas portlets overlay https://github.com/Jasig/uPortal/blob/uportal-4.0.13/uportal-portlets-overlay/cas/src/main/resources/log4j.xml. Not sure why that is. I'd think you'd want cas to do some logging for those infrequent use cases where you have a local cas server (typically you'd have a separate CAS server except when doing local development, demos, etc.). Eric, replace the <sourceRoot>/uportal-portlets-overlay/cas/src/main/resources/log4j.xml with this version that's in uportal master https://github.com/Jasig/uPortal/blob/master/uportal-portlets-overlay/cas/src/main/resources/log4j.xml. Then you should get you the log file. James Wennmacher - Unicon 480.558.2420 On 04/11/2014 03:52 AM, Eric ATTOU wrote: > Andrew Petro<[email protected]> a ??crit : > >> Eric, >> >> The most immediate question is, why isn't your CAS server logging >> somewhere you like? >> >> So. In your Tomcat/webapps/cas/WEB-INF/classes/ directory, there ought >> to be a log4j.xml file. >> >> Here's mine:https://gist.github.com/apetro/10413563 >> >> What's yours look like, and want to hard code > Hello Andrew > > Below is what mine looks like. i don't have the <param name="File" ...> setted > inside. But i set environment.build.log variables in uPortal/filters files. > > #######log4j.xml###################################################################### > <?xml version="1.0" encoding="UTF-8" ?> > <!-- > > Licensed to Jasig under one or more contributor license > agreements. See the NOTICE file distributed with this work > for additional information regarding copyright ownership. > Jasig licenses this file to you under the Apache License, > Version 2.0 (the "License"); you may not use this file > except in compliance with the License. You may obtain a > copy of the License at: > > http://www.apache.org/licenses/LICENSE-2.0 > > Unless required by applicable law or agreed to in writing, > software distributed under the License is distributed on > an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > KIND, either express or implied. See the License for the > specific language governing permissions and limitations > under the License. > > --> > > <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> > > <log4j:configuration debug="false" > xmlns:log4j="http://jakarta.apache.org/log4j/";> > > <!-- > Log file variables, such as "{environment.build.log.rootLevel}" > are defined > by properties in the uPortal/filters directory. See the Building > and Deploying uPortal section of the uPortal manual > --> > > <!-- > This default ConsoleAppender is used to log all NON perf4j messages > to System.out > --> > <appender name="null" class="org.apache.log4j.varia.NullAppender" /> > > <!-- Loggers --> > <!-- > The Perf4J logger. Note that org.perf4j.TimingLogger is the value of > the > org.perf4j.StopWatch.DEFAULT_LOGGER_NAME constant. Also, note that > additivity is set to false, which is usually what is desired - > this means > that timing statements will only be sent to this logger and NOT to > upstream loggers. > --> > <logger name="org.perf4j.TimingLogger" additivity="false"> > <level value="INFO"/> > <appender-ref ref="null"/> > </logger> > > <!-- > WARNING: Setting the org.springframework logger to DEBUG > displays debug information about > the request parameter values being bound to the command > objects. This could expose your > password in the log file. If you are sharing your log files, > it is recommend you selectively > apply DEBUG level logging on a an org.springframework.* > package level (i.e. org.springframework.dao) > --> > <logger name="org.springframework"> > <level value="WARN" /> > </logger> > > <logger name="org.springframework.webflow"> > <level value="WARN" /> > </logger> > > <logger name="org.jasig" additivity="true"> > <level value="DEBUG" /> > <appender-ref ref="null" /> > </logger> > > <!-- > WARNING: Setting the flow package to DEBUG will display > the parameters posted to the login servlet including > cleartext authentication credentials > --> > <logger name="org.jasig.cas.web.flow" additivity="true"> > <level value="INFO" /> > <appender-ref ref="null" /> > </logger> > > <!-- > The root logger sends all log statements EXCEPT those sent to the > perf4j > logger to System.out. > --> > <root> > <level value="INFO"/> > <appender-ref ref="null"/> > </root> > </log4j:configuration> > #############End > log4j.xml############################################################## > > and here is my log setting in local.filters > # Logs > > environment.build.log.logfileDirectory=/etc/uportal-tomcat/logs > environment.build.log.logfileName=uPortal.log > environment.build.log.size=1024 > environment.build.log.rootLevel=INFO > environment.build.log.layoutConversionPattern=[${environment.build.host.logicalName}]%5p > [%t] %d{MMM/dd HH:mm:ss,SSS} %c{2}.[%x] - > %m%n > environment.build.log.rollingLogFileDatePattern=yyyy-MM-dd-HH > > > > > > > >> <paramname="File"value="${catalina.base}/logs/cas.log"/> >> >> to point to a path you really like? >> >> --- >> >> Does this directory server: >> >> ldap://directoryserver.uac.bj >> >> let you bind over ldap: rather than ldaps: ? If I were that LDAP >> server, I would require ldaps: :) > The directory server allows bind over ldap. >> --- >> >> What uPortal version did you start from? > I'm using uPortal 4.0.13 > > Thanks a lot for your help. >> Kind regards, >> >> Andrew >> >> >> >> >> >> >> >> >> >> On 4/10/14, 11:22 AM, Eric ATTOU wrote: >>> Andrew Petro<[email protected]> a ??crit : >>> >>>> Eric, >>>> >>>> Are you saying you're able to log in with successful LDAP >>>> integration, and then you comment out the warning message in the CAS >>>> login JSP, and then you're no longer able to log in with successful >>>> LDAP integration? >>> Whether i comment out the warning message or not in the CAS login JSP, >>> i don't succeed, logging. And i don't know how to troubleshout this >>> issue. >>> Here are my LDAP integration settings in deployment.xml >>> >>> #################### LDAP Bind bean definition ###################### >>> <bean class="org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler" > >>> <property name="filter" >>> value="uid=%u" /> >>> <property name="searchBase" >>> value="dc=uac,dc=bj" /> >>> <property name="scope" value="sub" /> >>> <property name="contextSource" >>> ref="contextSource" /> >>> </bean> >>> >>> and contextSource definition bean >>> >>> #################### contextSource bean definition ###################### >>> <bean id="contextSource" >>> class="org.springframework.ldap.core.support.LdapContextSource" > >>> <property name="url" >>> value="ldap://directoryserver.uac.bj"; >>> /> >>> <property name="userDn" >>> value="cn=manager,dc=uac,dc=bj" /> >>> <property name="password" value="xxxxxxx" /> >>> <property name="baseEnvironmentProperties"> >>> <map> >>> <entry >>> key="com.sun.jndi.ldap.connect.timeout" value="3000" /> >>> <entry key="com.sun.jndi.ldap.read.timeout" >>> value="3000" /> >>> <entry >>> key="java.naming.security.authentication" value="simple" /> >>> </map> >>> </property> >>> </bean> >>> >>> Someone told me on the list that i must have a CAS log file which show >>> what's wrong. >>> But i don't see no such file in my tomcat log dir. >>> >>> Why CAS log file is not produced? >>> >>> >>> Thanks a lot for your help. >>>> That would be strange, but would be pretty easy to troubleshoot: in >>>> that case, provide your before and after login JSP, preferably as a >>>> gist or gists, and there's probably a typo in the commenting out >>>> that'll be feasible to spot. >>>> >>>> If you're saying you've got two independent problems (1. tweaking >>>> the login JSP, 2. configuring CAS for LDAP integration), great, >>>> separate the problems. :) The UI warning about insecure channel is >>>> totally unrelated to whether and how CAS might be configured to >>>> validate passwords against LDAP. >>>> >>>> To the extent that you're troubleshooting not-uPortal-specific >>>> issues with CAS configuration, consider asking for help on the CAS >>>> project users' list.http://www.apereo.org/cas/mailing-lists >>>> >>>> Andrew >>>> >>>> >>>> >>>> >>>> On 4/9/14, 12:12 PM, Eric ATTOU wrote: >>>>> Andrew Petro<[email protected]> a ??crit : >>>>> >>>>>> Eric, >>>>>> >>>>>> Demo on your laptop on port 8080 over http. >>>>>> >>>>>> Comment out the warning markup in the CAS login page JSP. >>>>>> >>>>> Thanks Andrew, >>>>> >>>>> When i comment it out and try logging after providing my login >>>>> and password, i can't pass authentication and i don't know what's >>>>> wrong. Below are the last lines in my catalina.out >>>>> >>>>> avr. 09, 2014 5:50:13 PM org.apache.coyote.AbstractProtocol start >>>>> INFO: Starting ProtocolHandler ["http-bio-8080"] >>>>> avr. 09, 2014 5:50:13 PM org.apache.coyote.AbstractProtocol start >>>>> INFO: Starting ProtocolHandler ["ajp-bio-10.0.128.35-8009"] >>>>> avr. 09, 2014 5:50:13 PM org.apache.catalina.startup.Catalina start >>>>> INFO: Server startup in 103972 ms >>>>> log4j:WARN No appenders could be found for logger >>>>> (org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl). >>>>> log4j:WARN Please initialize the log4j system properly. >>>>> log4j:WARN Seehttp://logging.apache.org/log4j/1.2/faq.html#noconfig >>>>> for more info. >>>>> start[1397058912258] time[125] tag[PersonDirAuthenticationHandler] >>>>> >>>>> I'm trying to authenticate against LDAP directory and i don't have >>>>> >>>>> any cas.log to see what's wrong with the authentication. >>>>> >>>>>> That'll work demo deep. The warning is there to >>>>>> 1. Remind you to implement SSL sometime between now and >>>>>> production. :), and >>>>>> 2. Explain why single sign-on isn't going to work. You'll have to >>>>>> type username and password again every time you log in instead of >>>>>> enjoying a CAS single sign-on session because CAS, at least by >>>>>> default, tells your browser to send the single sign-on session >>>>>> cookie only over a secure channel. >>>>>> >>>>>> Kind regards, >>>>>> >>>>>> Andrew >>>>>> >>>>>> >>>>>> >>>>>> On 4/9/14, 11:22 AM, Eric ATTOU wrote: >>>>>>> I stopped the apache web server since i don't need it. >>>>>>> >>>>>>> I saw the extra charater in front of my Connector tag and >>>>>>> >>>>>>> removed it. >>>>>>> James Wennmacher<[email protected]> a ??crit : >>>>>>> >>>>>>>> There is value to leaving in port 8080; it can be redirected to 8443 >>>>>>>> for you (though be careful as I see you have an extra character >>>>>>>> <!Connector). Do you have apache httpd fronting tomcat? That is >>>>>>>> often running on port 80. If you do have apache httpd in front, you >>>>>>>> would need to configure https for httpd not tomcat. See the apache >>>>>>>> docs. >>>>>>>> >>>>>>>> Do you need https for your local config or what are you trying to do? >>>>>>> I just want to have a typical uportal environment up and >>>>>>> running on my >>>>>>> laptop in order to make a demo to the head of our university to convince >>>>>>> them to invest in its deployment. For now, it's running but when i try >>>>>>> logging in, it show me the warning saying that Single Sign-On will not >>>>>>> work over non-secure connexion. >>>>>>> >>>>>>> Thanks for your help >>>>>>>> James Wennmacher - Unicon >>>>>>>> 480.558.2420 >>>>>>>> >>>>>>>> On 04/09/2014 03:04 AM, Eric ATTOU wrote: >>>>>>>>> Hello James >>>>>>>>> >>>>>>>>> James Wennmacher<[email protected]> a ??crit : >>>>>>>>> >>>>>>>>>> I see. You are using the bundled CAS server on the same >>>>>>>>>> machine uPortal >>>>>>>>>> is running on. Typically in local configuration we run with HTTP and >>>>>>>>>> not HTTPS because we use the local configuration for development and >>>>>>>>>> don't want to mess with installing certs, etc. For test or prod you >>>>>>>>>> would do something like: >>>>>>>>>> 1. (small installation, no fault tolerance or redundancy, not >>>>>>>>>> recommended) run tomcat with HTTPS ( >>>>>>>>>> https://wiki.jasig.org/display/UPM40/SSL+Configuration) and have both >>>>>>>>>> uPortal and CAS on the same server using HTTPS, or >>>>>>>>> For instance, since i'm in a test environment, i follow the wiki above >>>>>>>>> to configure tomcat >>>>>>>>> with https.Below is my connector section in server.xml >>>>>>>>> >>>>>>>>> <!-- A "Connector" represents an endpoint by which requests >>>>>>>>> are received >>>>>>>>> and responses are returned. Documentation at : >>>>>>>>> Java HTTP Connector: /docs/config/http.html (blocking & >>>>>>>>> non-blocking) >>>>>>>>> Java AJP Connector: /docs/config/ajp.html >>>>>>>>> APR (HTTP/AJP) Connector: /docs/apr.html >>>>>>>>> Define a non-SSL HTTP/1.1 Connector on port 8080 >>>>>>>>> --> >>>>>>>>> <!--Connector port="8080" protocol="HTTP/1.1" >>>>>>>>> connectionTimeout="20000" >>>>>>>>> redirectPort="8443" /--> >>>>>>>>> <!-- A "Connector" using the shared thread pool--> >>>>>>>>> <!-- >>>>>>>>> <!Connector executor="tomcatThreadPool" >>>>>>>>> port="8080" protocol="HTTP/1.1" >>>>>>>>> connectionTimeout="20000" >>>>>>>>> redirectPort="8443" /> >>>>>>>>> --> >>>>>>>>> <!-- Define a SSL HTTP/1.1 Connector on port 8443 >>>>>>>>> This connector uses the JSSE configuration, when >>>>>>>>> using APR, the >>>>>>>>> connector should be using the OpenSSL style configuration >>>>>>>>> described in the APR documentation --> >>>>>>>>> <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" >>>>>>>>> address="10.0.128.35" >>>>>>>>> maxHttpHeaderSize="8192" minSpareThreads="25" >>>>>>>>> maxSpareThreads="75" >>>>>>>>> enableLookups="false" disableUploadTimeout="true" >>>>>>>>> maxThreads="150" scheme="https" secure="true" >>>>>>>>> clientAuth="false" sslProtocol="TLS" /> >>>>>>>>> >>>>>>>>> <!-- Define an AJP 1.3 Connector on port 8009 --> >>>>>>>>> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" >>>>>>>>> /> >>>>>>>>> >>>>>>>>> But since then uportal is neither accessible from port 8080 nor >>>>>>>>> from 8443. It >>>>>>>>> is running on port 80 instead. >>>>>>>>> >>>>>>>>> What am i missing ? >>>>>>>>> >>>>>>>>> Thanks for your help. >>>>>>>>> >>>>>>>>>> 2. (normal or large installation) have a load balancer in >>>>>>>>>> front of 1 or >>>>>>>>>> more uPortal servers with HTTPS terminated on the load balancer and >>>>>>>>>> separate, clustered CAS servers configured for HTTPS. >>>>>>>>>> There are other variations with Apache httpd, and it also >>>>>>>>>> depends upon >>>>>>>>>> how you choose to do authentication, if you need CAS ClearPass, etc. >>>>>>>>>> >>>>>>>>>> The warning displayed by the CAS server is appropriate; you >>>>>>>>>> don't want >>>>>>>>>> to post user passwords in HTTP mode. Of course you typically >>>>>>>>>> only have >>>>>>>>>> this setup in your local/dev configuration where it typically doesn't >>>>>>>>>> matter. >>>>>>>>>> >>>>>>>>>> James Wennmacher - Unicon >>>>>>>>>> 480.558.2420 >>>>>>>>>> >>>>>>>>>> On 04/08/2014 10:29 AM, Eric ATTOU wrote: >>>>>>>>>>> James Wennmacher<[email protected]> a ??crit : >>>>>>>>>>> >>>>>>>>>>>> Hard to say what is not right. Suggestions: >>>>>>>>>>>> >>>>>>>>>>>> 1. Are doing a local build (specifying -Denv=local or not >>>>>>>>>>>> specifying >>>>>>>>>>>> env at all on the ant command)?. By default the build will use >>>>>>>>>>>> filters/local.properties. To build for test you'd do >>>>>>>>>>>> something like >>>>>>>>>>>> ant -Denv=test clean deploy-ear (or initportal to initialize the >>>>>>>>>>>> database as well). >>>>>>>>>>> I just issue 'ant clean deploy-war' without any -Denv >>>>>>>>>>> specification. >>>>>>>>>>> >>>>>>>>>>>> 2. Look at your >>>>>>>>>>>> webapps/uPortal/WEB-INF/classes/properties/security.properties in >>>>>>>>>>>> your tomcat deployment. Verify it matches what you expect (e.g. >>>>>>>>>>>> https is present in CAS URLs). >>>>>>>>>>> my >>>>>>>>>>> webapps/uPortal/WEB-INF/classes/properties/security.properties >>>>>>>>>>> match >>>>>>>>>>> what i expect since all cas URL there have https as protocol. >>>>>>>>>>> Here are URLs >>>>>>>>>>> directives in that file: >>>>>>>>>>> >>>>>>>>>>> ## unescaped URL and since there are no further parameters on the >>>>>>>>>>> logout URL, this does work. >>>>>>>>>>> logoutRedirect.root=https://localhost/cas/logout?service=http://localhost/uPortal/Login >>>>>>>>>>> >>>>>>>>>>> ## Login URL, if specified the CLogin channel will display a >>>>>>>>>>> Login link with >>>>>>>>>>> ## this URL instead of the standard userName/password form. >>>>>>>>>>> org.jasig.portal.channels.CLogin.CasLoginUrl=https://localhost/cas/login?service=http://localhost/uPortal/Login >>>>>>>>>>> >>>>>>>>>>> ## URL of the CAS clearPass password service >>>>>>>>>>> #org.jasig.portal.security.provider.cas.clearpass.PasswordCachingCasAssertionSecurityContextFactory.clearPassCasUrl==https://localhost/cas/clearPass >>>>>>>>>>> >>>>>>>>>>> The problem is that my cas seams actually not running on >>>>>>>>>>> https but on >>>>>>>>>>> http instead >>>>>>>>>>> >>>>>>>>>>> since when i click the login button on uPortal home page, i'm >>>>>>>>>>> redirected to >>>>>>>>>>> >>>>>>>>>>> https://localhost/cas/login?service=http://localhost/uPortal/Login >>>>>>>>>>> >>>>>>>>>>> but this page prompt me a 'Connection failure' and i used to >>>>>>>>>>> change the >>>>>>>>>>> >>>>>>>>>>> redirection url to >>>>>>>>>>> http://localhost/cas/login?service=http://localhost/uPortal/Login >>>>>>>>>>> >>>>>>>>>>> before accessing cas authentication page which send the >>>>>>>>>>> warning message: >>>>>>>>>>> >>>>>>>>>>> "Non-secure Connection >>>>>>>>>>> >>>>>>>>>>> You are currently accessing CAS over a non-secure connection. Single >>>>>>>>>>> Sign On WILL NOT WORK. In order to have single sign on >>>>>>>>>>> work, you MUST >>>>>>>>>>> log in over HTTPS". >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks! >>>>>>>>>>> >>>>>>>>>>>> James Wennmacher - Unicon >>>>>>>>>>>> 480.558.2420 >>>>>>>>>>>> >>>>>>>>>>>> On 04/08/2014 09:47 AM, Eric ATTOU wrote: >>>>>>>>>>>>> James Wennmacher<[email protected]> a ??crit : >>>>>>>>>>>>> >>>>>>>>>>>>>> In your filters/*.properties file there is an >>>>>>>>>>>>>> environment variable >>>>>>>>>>>>>> environment.build.cas.protocol >>>>>>>>>>>>>> set it to https then do an ant clean deploy-ear. It will >>>>>>>>>>>>>> substitute >>>>>>>>>>>>>> the variables into the security.properties file and uPortal will >>>>>>>>>>>>>> redirect the browser to an HTTPS CAS URL. >>>>>>>>>>>>> Here is the entries in my filters/*.properties >>>>>>>>>>>>> >>>>>>>>>>>>> # CAS server configuration properties >>>>>>>>>>>>> environment.build.cas.server=localhost >>>>>>>>>>>>> environment.build.cas.protocol=https >>>>>>>>>>>>> environment.build.cas.context=/cas >>>>>>>>>>>>> >>>>>>>>>>>>> I unsuccessfully do ant clean deploy-war many times >>>>>>>>>>>>> >>>>>>>>>>>>> what may be wrong? >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks a lot >>>>>>>>>>>>>> Note: In the quick start and local builds we typically >>>>>>>>>>>>>> access CAS >>>>>>>>>>>>>> via http to avoid the hassle of dealing with certificates. You >>>>>>>>>>>>>> definitely use HTTPS on prod and test. >>>>>>>>>>>>>> >>>>>>>>>>>>>> James Wennmacher - Unicon >>>>>>>>>>>>>> 480.558.2420 >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 04/08/2014 07:03 AM, Eric ATTOU wrote: >>>>>>>>>>>>>>> Hi everybody on the list! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I'm encountering an the following warning while loading the >>>>>>>>>>>>>>> authentication page of >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> jasig cas from uportal: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> "NON-SECURE CONNECTION >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> YOU ARE CURRENTLY ACCESSING CAS OVER A NON-SECURE CONNECTION. >>>>>>>>>>>>>>> SINGLE SIGN >>>>>>>>>>>>>>> ON WILL NOT WORK. IN ORDER TO HAVE SINGLE SIGN ON WORK, YOU >>>>>>>>>>>>>>> MUST LOG IN >>>>>>>>>>>>>>> OVER HTTPS." >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> How did configure uportal and jasig cas over a secure >>>>>>>>>>>>>>> connection? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks a lot. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> --- You are currently subscribed to >>>>>>>>>>>>>> [email protected] as: >>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>> To unsubscribe, change settings or access archives, see >>>>>>>>>>>>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >>>>>>>>>>>> --- You are currently subscribed to >>>>>>>>>>>> [email protected] as: >>>>>>>>>>>> [email protected] >>>>>>>>>>>> To unsubscribe, change settings or access archives, see >>>>>>>>>>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >>>>>>>>>> --- >>>>>>>>>> You are currently subscribed [email protected] as: >>>>>>>>>> [email protected] >>>>>>>>>> To unsubscribe, change settings or access archives, see >>>>>>>>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >>>>>>>> --- You are currently subscribed [email protected] as: >>>>>>>> [email protected] >>>>>>>> To unsubscribe, change settings or access archives, see >>>>>>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >>>>>> --- You are currently subscribed [email protected] as: >>>>>> [email protected] >>>>>> To unsubscribe, change settings or access archives, see >>>>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >>>> --- You are currently subscribed [email protected] as: >>>> [email protected] >>>> To unsubscribe, change settings or access archives, see >>>> http://www.ja-sig.org/wiki/display/JSG/uportal-user >> --- >> You are currently subscribed [email protected] as: >> [email protected] >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/uportal-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
