Chris & Eric,

It's an issue with smartLdap. The searchForGroups() method in smartLdap builds a regular expression from the name you search on, and it doesn't properly handle characters that are special in regular expression syntax.

Maybe we can put our heads together here at the unconference.

drew

Christopher Doyle wrote:
Actually, it does not appear to be a SQL exception:

Caused by: java.lang.RuntimeException: The specified member was not found: Active Directory (H1)

at org.jasig.portal.io.GetMemberServicePhrase.evaluate(GetMemberServicePhrase.java:84)

at org.danann.cernunnos.runtime.ConcatenatingPhrase.evaluate(ConcatenatingPhrase.java:77)

at org.danann.cernunnos.sql.PhraseParameterPreparedStatementSetter.setValues(PhraseParameterPreparedStatementSetter.java:40)

at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(JdbcTemplate.java:771)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:566)

at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:767)

at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:825)

    at org.danann.cernunnos.sql.UpsertTask.doUpdate(UpsertTask.java:167)

    at org.danann.cernunnos.sql.UpsertTask.perform(UpsertTask.java:147)

at org.danann.cernunnos.runtime.RuntimeTaskDecorator.perform(RuntimeTaskDecorator.java:58)

at org.danann.cernunnos.AbstractContainerTask.performSubtasks(AbstractContainerTask.java:123)

at org.danann.cernunnos.sql.TransactionTask.access$300(TransactionTask.java:40)

at org.danann.cernunnos.sql.TransactionTask$PerformSubtasksTransactionCallback.doInTransactionWithoutResult(TransactionTask.java:141)

at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33)

at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)

at org.danann.cernunnos.sql.TransactionTask.perform(TransactionTask.java:115)

at org.danann.cernunnos.runtime.RuntimeTaskDecorator.perform(RuntimeTaskDecorator.java:58)

at org.danann.cernunnos.runtime.ScriptRunner$TaskDecorator.perform(ScriptRunner.java:310)

    at org.danann.cernunnos.runtime.ScriptRunner.run(ScriptRunner.java:264)

at org.danann.cernunnos.flow.CernunnosTask.perform(CernunnosTask.java:87)

    ... 27 more

I’m still thinking that handling the delimiting on the export side should do the trick. Or perhaps during the comparison in GetMemberServicePhrase.evaluate(). I’ll take a look at the scripts you committed to trunk as I proceed forth as well.

Thanks,

--Chris

*From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Eric Dalquist
*Sent:* Tuesday, October 07, 2008 11:26 AM
*To:* [email protected]
*Subject:* Re: [uportal-dev] Small Import/Export Concern

How did it fail? Was it a SQL exception?

If so Cernunnos 1.0 should be able to deal with the string since it uses prepared statements for the SQL. Also, all of the updated import scripts are in the trunk right now if you want to take a look.

-Eric

Christopher Doyle wrote:

I ran into a little issue when attempting to import a membership entity into uPortal where the relevant group name contains parentheses. In our case, we are using the following values to define the /ROOT_KEY/ value of our SmartLdapGroupStore (per environment):

Local / Development:     “Active Directory (H1)”

Staging / Production:      “Active Directory (WIN)”

We added this SmartLdapGroupStore ROOT group to the “Everyone” group using the Groups Manager. The subsequent exported membership entity (as generated by crn-export) is defined as:

<membership script="classpath://org/jasig/portal/io/import-membership_v2-6.crn">

  <parent>Everyone</parent>

  <child>

    <group>Active Directory (H1)</group>

  </child>

</membership>

My initial attempt to import this entity into a new environment failed. As it turns out, the parentheses in the /ROOT_KEY/ were the culprit. I manually delimited the parentheses in the entity and was able to re-run the import successfully:

    <group>Active Directory \(H1\)</group>

My proposal is obviously to modify the export .crn scripts to accommodate proper delimiting. I’m prepping a release at the moment and don’t have an immediate solution to contribute back, but wanted to at least make folks aware of the concern in case it comes up elsewhere.

Eric D. – I know that you have prepared some updated import/export scripts for 3.1.0, do they address this? I don’t want to duplicate any work that you may have already completed.

Thanks,

--Chris

--

[ c h r i s d o y l e ]

Johns Hopkins University

Sr. System Software Engineer, [EMAIL PROTECTED]

410.735.4127

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>

"Eleven. Exactly. One louder."

--

You are currently subscribed to [email protected] 
<mailto:[email protected]> as: [EMAIL PROTECTED] <mailto:[EMAIL 
PROTECTED]>

To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


--

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



--
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

Reply via email to