personally rather than repackage jamfconnect I just drop it in my own wrapper package, meaning I don't have to mess around with it each time it's updated, I just update the wrapper. Less chance of any issues.
I also deploy the graphic(s) for using with Jamf Connect Notify in here.
then in the post install script I install JC, setup initial notify values then sort out the login window;
# install Jamf Connect
installer -pkg "/var/tmp/JamfConnectLogin-1.1.2.pkg" -target /
# set initial notify values
/usr/local/bin/authchanger -reset -preLogin JamfConnectLogin:Notify
/bin/echo "Command: MainTitle: Configuring your Mac..." >> /var/tmp/depnotify.log
/bin/echo "Command: MainText: Configuring your Mac for use in MyOrg.
This won't take long and you don't need to do anything." >> /var/tmp/depnotify.log
/bin/echo "Command: Image: "/Library/Management/MyOrg/graphics/myorg-tr.png"" >> /var/tmp/depnotify.log
/bin/echo "Status: Please wait..." >> /var/tmp/depnotify.log
# Wait for the setup assistant to complete before continuing
log "Waiting for Setup Assistant to complete..."
loggedInUser=$(/usr/sbin/scutil <<< "show State:/Users/ConsoleUser" | /usr/bin/awk -F': ' '/[[:space:]]+Name[[:space:]]:/ { if ( $2 != "loginwindow" ) { print $2 }} ')
while [[ "$loggedInUser" == "_mbsetupuser" ]]; do
/bin/sleep 5
loggedInUser=$(/usr/sbin/scutil <<< "show State:/Users/ConsoleUser" | /usr/bin/awk -F': ' '/[[:space:]]+Name[[:space:]]:/ { if ( $2 != "loginwindow" ) { print $2 }} ')
done
# switch login window
killall loginwindowonce the installs are done you can switch login mechanisms back to either JC or default as required
