gcf

GCF Connector to dotnet app with dynamic session ID in URL

I'm attempting to build an SSO to an ASP.NET application that's dynamically inserting the session ID within the URL as follows:
https://www.myserver.net/(S(vchbbnqzsl9vmc424jg5vf33))/default.aspx

I've edited the XML file to use both the GRAB and GRABFROMHEADER tags with no luck.
GET a:url="http://www.myserver.net/" a:query="" a:redirects="yes"
SEARCH a:symbol="mylogin" a:source="${_RESPONSE}" a:value="${_VALUE}"
GRAB a:start=".net/" a:end="/defaultDesktop.aspx"
SEARCH


SET a:symbol="MYLOGIN" a:value="${mylogin}"

GCF SSL connector in Luminis 4

I am trying to get all the pieces in place to run an outside application that we wrote to run over SSL through the cpipconnector. I have a .properties file and .xml file set up. The .properties hostmame, pickup.remoterul and externalSystemURL are pointing at the https website. I have also set up the system in es.systems.secure.login. For a while I was getting the "CPIP Notification: Unsupported OID service" error. Now that I've changed some other settings, I'm getting an "Unknown error occurred" message.

GCF to Basic HTTP Auth is doable!

Have I found the holy grail of Luminis GFC developers? I have a fully functioning GCF connector that authenticates me to a system that uses basic http auth.

This trick relies on a special case, but it is hopefully universal enough that others would be interested.

How does this work?

GCF for Astra Schedule VII

Has anyone created a GCF for Astra Schedule VII? If so, would you share it with us? We are running Luminis 4.2.2.

Thanks,
Ron

GCF connection to Blackboard 8

Has anybody gotten a single signon connection to Blackboard 8 to work? If so would you mind sharing your setup?

Any other Luminis III schools utilizing port 80/443 for CPIP in single-server setting?

I've reviewed all of the content on LDN re: moving CPIP to port 80/443 but nothing I've found applies exactly to my situation. For one, we're still using Luminis III (on Solaris). Secondly, we have a 1 server environment.

I attempted to follow Sungard FAQ 1-54G63I (which is for Luminis IV) but ran into a snag with modifying the server.xml. I've backed out of those mods and moved on to plan B.

Plan B is having another IP bound to the server's network adapter and modifying the configuration for CPIP to use port 80/443 on this other IP. So far this hasn't worked either.

Custom Class issue with GCF

Greetings All,

I am working on creating a custom class that will DES, then BASE64 encrypt a string and pass it back to the GCF for posting. The JAVA compiles fine, but won't run on the command-line. It is based on Sungard's Sample.java file found in /opt/luminis/webapps/cpipconnector/WEB-INF/config/sample/. I've created the class file in /opt/luminis/webapps/cpipconnector/WEB-INF/classes/com/campuspipeline/sso/authenticator/custom/ as directed by Sungard Support. However, when it is run on the command-line, I receive the following error:

 

Has anyone developed a gmail GCF SSO (eg, not using google api/SAML)?

Has anyone developed a gmail/google apps GCF SSO?  Or an SSO that does not make it so that the only way a user can login to gmail/google apps is via luminis?

Looking at the gmail/google apps web form, there are (at least) two variables that change every time you go to the form (dsh & GALX).... so a simple GCF isn't in the cards.

Need to prepopulate Luminis IV Secret Store with External System Passwords

Hello all,

 

We have an external application called WebStudy which we have setup a GCF for using pickup.html on the remote server. Right now we are using autosync=true which means the user is responsible for putting in their own username and password. We would like to prepopulate all accounts in Luminis with their login/password. The login is the same as the Luminis login. The password will be random. I think I can accomplish this by using cptool:

GCF to Google Apps using SimpleSAML

We have set up Google Apps for Education using SAML authentication to authenticate against Active Directory. We are using simpleSAML as our Identify Provider and it is installed on a separate server from Luminis. Both simpleSAML and Luminis authenticate against Active Directory, so the password should be the same in both systems.

Syndicate content