Description

Documentation can be found at: https://www.kimai.org/documentation/ldap.html

Features:

• Authenticate against an LDAP
• New users will be created on the fly
• Configured attributes will be synced on every login
• Mapping LDAP groups to Kimai roles is possible

TODO

• [x] prevent setting an internal password
• [x] get rid of the service class name parameter
• [x] convert ldap container parameter to config class
• [x] add group mapping query

How to test

• checkout the branch
• composer install
• adjust config/packages/local.yaml to your needs (see documentation)
• bin/console cache:clear

Open questions for EVERY reader

• How do other apps handle LDAP support?
• Should an app still offer registration when LDAP is activated?
  • Leave that configurable or turn it off always?
  • I guess we need to avoid problems like a local account with the same account name in LDAP, then the LDAP account would never be checked?
• Should groups be transferred?
  • How? Is there a general approach?
  • I read something about a "memberof" field/attribute which seems to only a OpenLDAP feature?
• The login needs to be checked against LDAP every time?
• What should happen to the local account if an account in LDAP is deleted?
• Can LDAP accounts be deactivated?

If anything else comes to your mind, please share it. This is one of the features I have to develop without having a proper LDAP setup/knowledge, so I am "flying blindly" here and need YOUR input.

Fixes #193 Fixes #795 Fixes #449

Types of changes

• [x] New feature (non-breaking change which adds functionality)

Checklist

• [x] I verified that my code applies to the guidelines (composer code-check)
• [x] I updated the documentation (see here)
• [x] I agree that this code is used in Kimai and will be published under the MIT license

Description

Only tested with Google apps SAML implementation

In order to test this branch, do a checkout and then:

• composer install
• edit config/packages/local.yaml with the adjusted contents below
• bin/console cache:clear --env=prod
• bin/console cache:warmup --env=prod
• Test the new login button ...

YOU FIND THE REQUIRED CONFIGURATION IN THE DOCUMENTATION See https://www.kimai.org/documentation/saml.html

Fixes #1227

Links:

• Dynatrace: Setup groups in G Suite
• Google: Creating custom attributes using the user schema

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] I verified that my code applies to the guidelines (composer kimai:code-check)
• [ ] I updated the documentation (see here)
• [x] I agree that this code is used in Kimai and will be published under the MIT license

Hi Just finished Polish traslation for Kimai. Before release to public via GitHub -wanted my users to review translation. But polish language does not apperar in language drop down list . Files added in kimai/translation :about.pl.xlf, daterangepicker.pl.xlf,flashmessages.pl.xlf,invoice-numbergenerator.pl.xlf, messages.pl.xlf, plugins.pl.xlf, tags.pl.xlf,validators.pl.xlf,actions.pl.xlf,exceptions.pl.xlf,invoice-calculator.pl.xlf, invoice-renderer.pl.xlf, pagerfanta.pl.xlf ,system-configuration.pl.xlf, teams.pl.xlf Files added in kimai2/vendor/kevinpapst/adminlte-bundle/Resources/translations/ AdminLTEBundle.pl.xliff config/packages/kimai.yaml not adjusted - there is no reason assuming fallback to en config/services.yaml adjusted app.js , callendar.js adjuster nginx reloaded . No languade in drop down . Do I miss something ? Reg - Mik

Describe the bug Getting the following error when doing an upgrade using, please help

root@chittar /var/www/kimai2.1 # git fetch --tags remote: Enumerating objects: 4769, done. remote: Counting objects: 100% (3575/3575), done. remote: Compressing objects: 100% (723/723), done. remote: Total 2396 (delta 1882), reused 2087 (delta 1642), pack-reused 0 Receiving objects: 100% (2396/2396), 3.08 MiB | 7.55 MiB/s, done. Resolving deltas: 100% (1882/1882), completed with 295 local objects. From https://github.com/kevinpapst/kimai2

• [new tag] 1.0 -> 1.0 root@chittar /var/www/kimai2.1 # git checkout 1.0 Previous HEAD position was 6dc4fa0 fix tests that failed around midnight (#735) HEAD is now at 94e49ea updated Spanish translations (#906)

root@chittar /var/www # chown -R www-data: kimai2.1/
Logfile

root@chittar /var/www/kimai2.1 # sudo -u www-data composer install --no-dev --optimize-autoloader
Cannot create cache directory /root/.composer/cache/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /root/.composer/cache/files/, or directory is not writable. Proceeding without cache
Cannot create cache directory /root/.composer/cache/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /root/.composer/cache/repo/https---repo.packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /root/.composer/cache/repo/https---flex.symfony.com/, or directory is not writable. Proceeding without cache
Loading composer repositories with package information
Installing dependencies from lock file
Package operations: 1 install, 52 updates, 3 removals
  - Removing symfony/security-core (v4.2.7)
  - Removing symfony/security-csrf (v4.2.7)
  - Removing symfony/security-guard (v4.2.7)
  - Updating symfony/flex (v1.2.3 => v1.2.5): Downloading (100%)         
  - Updating beberlei/doctrineextensions (v1.2.0 => v1.2.1): Downloading (100%)         
  - Updating symfony/routing (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/http-foundation (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/contracts (v1.0.2 => v1.1.1): Downloading (100%)         
  - Updating symfony/event-dispatcher (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/debug (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/http-kernel (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/finder (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/filesystem (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/dependency-injection (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/config (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/var-exporter (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/cache (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/framework-bundle (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/doctrine-bridge (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/console (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating doctrine/doctrine-bundle (1.10.2 => 1.11.1): Downloading (100%)         
  - Updating egulias/email-validator (2.1.7 => 2.1.8): Downloading (100%)         
  - Updating jms/serializer (2.3.0 => 3.0.1): Downloading (100%)         
  - Updating twig/twig (v2.8.1 => v2.11.0): Downloading (100%)         
  - Updating symfony/inflector (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/property-access (v4.2.7 => v4.2.9): Downloading (100%)         
  - Removing symfony/security-http (v4.2.7)
  - Installing symfony/security (v4.2.8): Downloading (100%)         
  - Updating symfony/options-resolver (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating kevinpapst/adminlte-bundle (2.6 => 2.8.1): Downloading (100%)         
  - Updating nikic/php-parser (v4.2.1 => v4.2.2): Downloading (100%)         
  - Updating phpdocumentor/reflection-docblock (4.3.0 => 4.3.1): Downloading (100%)         
  - Updating phpoffice/phpspreadsheet (1.6.0 => 1.7.0): Downloading (100%)         
  - Updating symfony/var-dumper (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/twig-bridge (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/debug-bundle (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/dotenv (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/expression-language (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/intl (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/form (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/monolog-bridge (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/property-info (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/security-bundle (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/serializer (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/stopwatch (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/swiftmailer-bundle (v3.2.6 => v3.2.7): Downloading (100%)         
  - Updating symfony/templating (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/translation (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/validator (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/twig-bundle (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/web-profiler-bundle (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/process (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/web-server-bundle (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating symfony/yaml (v4.2.7 => v4.2.9): Downloading (100%)         
  - Updating zircote/swagger-php (2.0.13 => 2.0.14): Downloading (100%)         
  - Updating symfony/asset (v4.2.7 => v4.2.9): Downloading (100%)         
  - Installing symfony/webpack-encore-bundle (v1.6.0): Downloading (100%)         
Generating optimized autoload files
ocramius/package-versions:  Generating version class...
ocramius/package-versions: ...done generating version class
Executing script cache:clear [KO]
 [KO]
Script cache:clear returned with error code 255
!!  PHP Fatal error:  Class 'Symfony\Component\Security\Core\Authorization\ExpressionLanguage' not found in /var/www/kimai2.1/vendor/sensio/framework-extra-bundle/Security/ExpressionLanguage.php on line 21
!!  
Script @auto-scripts was called via post-install-cmd

Hi/Hallo/Servus everyone! First of all thanks for this geenius project ;). I found Kimai 2 days ago so I'm completly new to this.

My idea is to connect kimai to RFID readers:

(0. Kimai already installed)

1. Buy a cheap ESP8266 microcontroller
2. Flash firmware
3. Connect cheap RFID modul to it
4. Login on the ESP8266 WiFi interface and connect it to the running kimai
5. Link RFID IDs to user and or activities
6. User presence: start tracking / stop tracking of presence (and last activity)

I tried out some API stuff and also read the dev docu but I can't find a clear entry point to start a plugin development.

Actually I have these ideas to do it:

1. Connect directly to database via subserver thats receiving the ID's and managing trackings
2. Write a plugin to manage RFID IDs and try to use the API (would be the best)
3. Use a subserver and use the API
4. Just add a new RFID field to users and use the API (but maybe without good error handling)

Things I can: Electronics, C, C++, C#, Java, Python, SQL

Things I need:

1. Link RFID IDs to user
2. Requesting with an RFID ID Kimai
3. Kimai does the handling of the tracking
4. Kimai responses with a state: start/stop(maybe with duration)/fail(maybe reason)

I would push the source code and shematics of the ESP8266 stuff on GitHub and when I get into the developing of a plugin that stuff too.

But first I want to ask you for suggestions to this or help how to get into the development and what I'll need to build. Because I really start at 0 in PHP coding :D

Greetings Alex

Describe the bug I installed the app locally and then uploaded all the files. Tried to navigate to the public folder and got a page 500 error and checked to see what error was causing it and was given the following:

Uncaught Twig_Error_Loader: The "/home/south287/public_html/timeclock2.0/kimai2\vendor\symfony\framework-bundle/Resources/views" directory does not exist ("/home/south287/public_html/timeclock2.0/kimai2\vendor\symfony\framework-bundle/Resources/views"). in /home/south287/public_html/timeclock2.0/kimai2/vendor/twig/twig/lib/Twig/Loader/Filesystem.php:101 Stack trace: #0 /home/south287/public_html/timeclock2.0/kimai2/var/cache/prod/ContainerJSVbq8m/srcProdProjectContainer.php(711): Twig_Loader_Filesystem->addPath('/home/south287/...', 'Framework') #1 /home/south287/public_html/timeclock2.0/kimai2/var/cache/prod/ContainerJSVbq8m/srcProdProjectContainer.php(1182): ContainerJSVbq8m\srcProdProjectContainer->getTwigService() #2 /home/south287/public_html/timeclock2.0/kimai2/var/cache/prod/ContainerJSVbq8m/srcProdProjectContainer.php(490): ContainerJSVbq8m\srcProdProjectContainer->getSensioFrameworkExtra_View_ListenerService() #3 /home/south287/public_html/timeclock2.0/kimai2/vendor/symfony/event-dispatcher/EventDisp in /home/south287/public_html/timeclock2.0/kimai2/vendor/twig/twig/lib/Twig/Loader/Filesystem.php on line 101

To Reproduce Steps to reproduce the behavior:

1. Installed locally
2. Uploaded all the files
3. Navigated to the public folder

Expected behavior App would be installed and running.

Screenshots None at the moment. I just see a white screen

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Chrome
• whatever the installed pulled from github

Smartphone (please complete the following information): NA

Additional context I installed locally as I have a shared server access to my website. I cannot install composer as I don't have root access.

First, I have to admit that I'm a bit lazy when it comes to updating the Kimai core – Plugins as soon as possible but not the core.

Some days ago I decided to update Kimai from cough 1.15.1 to the latest version. And this is where things started to go down the drain. Some operations where performed once and then quitted with a 503 error. Clearing the Kimai cache allowed exactly one operation and then failed again.

Same with API calls. The first request got a 200, the second one a 503.

No PHP errors where thrown.

I was able to duplicate the behaviour by just opening the calendar. First click worked, second quitted with a 503.

I then reverted back to 1.15.1 and everything was back to normal. An update to 1.15.2 did work flawlessly, too.

The errors came back when 1.15.3 was installed. Same behaviour as before.

14 days later I decided to go deep down this rabbit hole.

I installed a new Kimai instance, no data, no plugins. Version 1.15.2 worked without issues, 1.15.3 did show the exact behaviour as the "real" instance.

I then started to copy folders from the vendor folder over from 1.15.2 to 1.15.3 and long story short (or two days later)… Something seems to be badly wrong with the doctrine ORM.

If I replace the file

/vendor/doctrine/orm/lib/Doctrine/ORM/Query.php

with the version from Kimai 1.15.2 (and only this one file) everything is running back stable again.

Something must have changed which now causes trouble. I checked the ORM repository but couldn't find any issue that sounds familiar.

I did not dig any deeper, but I think it might be something related to MySQL 5.7 – but I'm not sure.

Just wanted to let you know that there's something going on – I stopped digging deeper at this point.

Kimai 1.16.2 seems to be running fine with the replaced Query.php.

Additional context

• PHP version: 7.4
• MySQL 5.7

I installed Kimai 1.6.2 in a Website within ISPConfig. I followed the instructions from the website using git and composer and everything went fine. I'm able to open the login page but I can't log in - im redirected to the login page. Registering a new user doesn't work as well but I can see, that the communication with the database is working because I can't register a user with the same name of an existing user. After submitting the form I receive the following error: "Der CSRF-Token ist ungültig. Versuchen Sie bitte das Formular erneut zu senden."

Any help is aprreciated.

Best regards, Thorsten

Describe the bug The installation was working properly, I tried to import an old database from Kimai 0.9, which did not work because of the version. I started to load and create the customers, projects, users manually. After I finished the day I closed it and next day I got the "critical error" message. I though I created an error with my import trials (despite unsuccessful). I whipped the DB with the commands: bin/console doctrine:schema:drop --force &&
bin/console doctrine:schema:create &&
After that I started again from zero and created some users and projects. Today as I want to log in I receive again the "critical error".

To Reproduce Steps to reproduce the behavior:

1. Create a new user from scratch.
2. Create new users, projects, etc.
3. Log out.
4. Log in again.

Logfile

[prod after drop db 04-06.log](https://github.com/kevinpapst/kimai2/files/4728541/prod.after.drop.db.04-06.log)

Screenshots

Desktop/Smartphone Please complete the following information if this seems to be a frontend issue:

Device: Synology DS718+
OS: DSM 6.2.2-24922 Update 4
Browser Firefox 76.0.1 (64-Bit)

Additional context Add any other context about the problem here.

Kimai version 2
PHP version 7.3
-DB MariaDB v10
-phpMyAdmin (PHP 5.6)

@kevinpapst I was trying to find a question template for this, as this is not a bug. I am currently working on an nginx-based docker image. However, I want to make the deployment as hassle free as possible, controlled by the docker ENV vars.

I am using a base image that allows me to specify a number of entry point scripts (to be executed on launch of the container). Everything works, but after the first time, as the script tries to create schema, migrations, admin user (specified in docker-compose) it is obviously going to fail. The container works just fine, though.

However, the schema:create command clearly specifies "do not run this on a production environment", I would assume because it might break it?

Therefore, I am looking for a graceful way to check for:

• Database exists.
• Update schema exists.
• Migration is up to date.
• First superadmin (local) user exists.

This, using preferable a simple bash script, but I am open to a php script as well.

I think I have also found a way to send the output of the current log (env/prod) to the stdout. The base image I have uses supervisor. If I put the tail of of the log into a supervisor job, it will live for the duration of the container, and will display wherever the container's stdout is shown.

Is your feature request related to a problem? Please describe. Often, customers have credit with me. In order to bill this correctly, it would be easy to add entries with negative fixed amounts

Describe the solution you'd like Allow negative fixed amounts when adding an entry

Describe alternatives you've considered Budget only shows, but does not affect billing or sums

Translations update from Hosted Weblate for Kimai - Time tracking/Main application.

It also includes following components:

• Kimai - Time tracking/Invoice-Templates

• Kimai - Time tracking/Validations

• Kimai - Time tracking/System configurations

• Kimai - Time tracking/Reporting

• Kimai - Time tracking/Plugins

• Kimai - Time tracking/Invoice-Numbers

• Kimai - Time tracking/Date-Picker

• Kimai - Time tracking/Emails

• Kimai - Time tracking/Wizard

• Kimai - Time tracking/Teams

• Kimai - Time tracking/User feedback (Flash messages and Alerts)

• Kimai - Time tracking/Export

• Kimai - Time tracking/Invoice-Calculator

• Kimai - Time tracking/About

• Kimai - Time tracking/Actions (Dropdowns and Toolbars)

Current translation status:

Description

A clear and concise description of what this pull request adds or changes.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [ ] I verified that my code applies to the guidelines (composer code-check)
• [ ] I updated the documentation (see here)
• [ ] I agree that this code is used in Kimai (see license)

Description

this release contains cleanups after 2.0, which will prevent rollbacks.

maybe this will make it into 2.0 final ... not sure yet.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] I verified that my code applies to the guidelines (composer code-check)
• [ ] I updated the documentation (see here)
• [x] I agree that this code is used in Kimai (see license)

Describe the issue

Using https://github.com/go-swagger/go-swagger:

./swagger_linux_amd64 generate client --spec doc.json
json: cannot unmarshal string into Go struct field SwaggerProps.definitions of type int64

doc.json is https://demo.kimai.org/api/doc.json

I already tried

• [X] I've read and searched the documentation.
• [X] I've searched for similar issues in this repository.
• [X] I've searched for similar issues in the discussions.

Kimai version

1.30.1

Which PHP version are you using?

7.3

How do you run Kimai?

kimai.cloud service

Steps to reproduce the behavior

1. Download go-swagger binary on https://github.com/go-swagger/go-swagger/releases
2. Run chmod +x on the binary
3. Download the 0.6 .json swagger spec from https://demo.kimai.org/api/doc.json
4. Run ./swagger_linux_amd64 generate client --spec doc.json

Logfile

No response

Screenshots

No response

Additional context

N/A

Describe the issue

Year only displayed with 3 digits, last is missing

I already tried

• [X] I've read and searched the documentation.
• [X] I've searched for similar issues in this repository.
• [X] I've searched for similar issues in the discussions.

Kimai version

2.0

Which PHP version are you using?

7.3

How do you run Kimai?

kimai.cloud service

Steps to reproduce the behavior

1. Go to '...'
2. Scroll down to '...'
3. Click on '...'
4. See error

Logfile

No response

Screenshots

Additional context

Device: [Ubuntu Laptop 16 inch, Windows Desktop 27 inch, iPhone 6s] Browser [e.g. Firefox 81, Chrome 85, Safari 14]

Describe the problem

An option to add attachments to weekly timesheets would be great. This will enable the user to attach files/images like customer approval for the time reported if its done via. email. The clients finance team might ask for approval to pay the invoice.

Describe the solution you'd like

Option to upload a file while reporting time on timesheets page and should be able to save. The uploaded file can be downloaded from timesheet reporting, if needed.

Describe alternatives you've considered

No response

Screenshots

No response