Installing osTicket 1.11 on Fedora 29
-
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
firewall-cmd --permanent --zone=FedoraServer --add-service=http
Leave off the
--zone
for the default zone. As this is different between versions. -
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
Any special SELinux after words? I had some issues with plugins the first time around.
Not using any plugins. I've not needed any SELinux tweaks afterwards myself.
I setup ldap for my install. Does it make sense to use it?
If you are in an LDAP based environment (AD, OpenLDAP, 389 Directory Server, OpenDJ) then joining your ticketing or helpdesk system to it would make total sense. We are not an LDAP shop here, so have nothing to attach it to.
-
@JaredBusch said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
firewall-cmd --permanent --zone=FedoraServer --add-service=http
Leave off the
--zone
for the default zone. As this is different between versions.Changed.
-
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
Any special SELinux after words? I had some issues with plugins the first time around.
Not using any plugins. I've not needed any SELinux tweaks afterwards myself.
I setup ldap for my install. Does it make sense to use it?
If you are in an LDAP based environment (AD, OpenLDAP, 389 Directory Server, OpenDJ) then joining your ticketing or helpdesk system to it would make total sense. We are not an LDAP shop here, so have nothing to attach it to.
The only thing I don't like about it so far is that you have to create the account first and select the option to authenticate with ldap. I wish I could just login with my creds and it would automatically create the account. Unless doing something wrong.
-
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
Any special SELinux after words? I had some issues with plugins the first time around.
Not using any plugins. I've not needed any SELinux tweaks afterwards myself.
I setup ldap for my install. Does it make sense to use it?
If you are in an LDAP based environment (AD, OpenLDAP, 389 Directory Server, OpenDJ) then joining your ticketing or helpdesk system to it would make total sense. We are not an LDAP shop here, so have nothing to attach it to.
The only thing I don't like about it so far is that you have to create the account first and select the option to authenticate with ldap. I wish I could just login with my creds and it would automatically create the account. Unless doing something wrong.
Is this for end users or for the techs? Normally we would not want techs being created automatically by just being included in the LDAP list. I can only imagine that it does not work that way intentionally. If it did, it would be very necessary to have a way to disable it.
-
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
Any special SELinux after words? I had some issues with plugins the first time around.
Not using any plugins. I've not needed any SELinux tweaks afterwards myself.
I setup ldap for my install. Does it make sense to use it?
If you are in an LDAP based environment (AD, OpenLDAP, 389 Directory Server, OpenDJ) then joining your ticketing or helpdesk system to it would make total sense. We are not an LDAP shop here, so have nothing to attach it to.
The only thing I don't like about it so far is that you have to create the account first and select the option to authenticate with ldap. I wish I could just login with my creds and it would automatically create the account. Unless doing something wrong.
Is this for end users or for the techs? Normally we would not want techs being created automatically by just being included in the LDAP list. I can only imagine that it does not work that way intentionally. If it did, it would be very necessary to have a way to disable it.
You can authenticate with staff and client. Probably makes sense to disable staff? I will be testing some more tomorrow.
-
Or else, of course, a way to specify which OU has been designated as which roles in osTicket.
-
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
@scottalanmiller said in Installing osTicket 1.11 on Fedora 29:
@mattbagan said in Installing osTicket 1.11 on Fedora 29:
Any special SELinux after words? I had some issues with plugins the first time around.
Not using any plugins. I've not needed any SELinux tweaks afterwards myself.
I setup ldap for my install. Does it make sense to use it?
If you are in an LDAP based environment (AD, OpenLDAP, 389 Directory Server, OpenDJ) then joining your ticketing or helpdesk system to it would make total sense. We are not an LDAP shop here, so have nothing to attach it to.
The only thing I don't like about it so far is that you have to create the account first and select the option to authenticate with ldap. I wish I could just login with my creds and it would automatically create the account. Unless doing something wrong.
Is this for end users or for the techs? Normally we would not want techs being created automatically by just being included in the LDAP list. I can only imagine that it does not work that way intentionally. If it did, it would be very necessary to have a way to disable it.
You can authenticate with staff and client. Probably makes sense to disable staff? I will be testing some more tomorrow.
But if it was automatic and accepted just everyone in the system, it would need more information. Doable, but more complicated.
-
@black3dynamite said in Installing osTicket 1.11 on Fedora 29:
Why not use git to install it? Wouldn’t that make updating it easier?
It is also not in their instructions.
Do they have a specific branch that matches the contents of the released
zip
? -
@JaredBusch said in Installing osTicket 1.11 on Fedora 29:
@black3dynamite said in Installing osTicket 1.11 on Fedora 29:
Why not use git to install it? Wouldn’t that make updating it easier?
It is also not in their instructions.
Do they have a specific branch that matches the contents of the released
zip
? -
@black3dynamite said in Installing osTicket 1.11 on Fedora 29:
@JaredBusch said in Installing osTicket 1.11 on Fedora 29:
@black3dynamite said in Installing osTicket 1.11 on Fedora 29:
Why not use git to install it? Wouldn’t that make updating it easier?
It is also not in their instructions.
Do they have a specific branch that matches the contents of the released
zip
?Even those instructions that mention the bleeding edge git pull method, then say to use the tarball for updates.
-
OSTicket is not a solution I can use, because I need time tracking also.
I never saw a plugin for that for OSTicket.