Recherche avancée

Sur d’autres sites (5017)

• Matomo SSO options and why is it useful ?

  8 novembre 2017, par Matomo Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Matomo (Piwik) at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Matomo has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Matomo (Piwik) features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Matomo (Piwik) plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Matomo (Piwik). It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://matomo.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Matomo (Piwik) account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Matomo (Piwik) can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Matomo (Piwik) with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Matomo (Piwik) for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Matomo (Piwik) core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Matomo (Piwik) is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Matomo.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.matomo.org/guides/getting-started-part-1.

• Problems writing to pipe in ffmpeg

  28 juin 2018, par Mikkel Bachmann

  I have written a stream server that utilizes FFMPEG for transcoding. [StreamServer2 v.1.5]

  The way it works is that i have thru a control channel tell a DVR to open a stream, when the stream is open the DVR will respond with a sdp file- or the info for the sdp file.
  This is working when i run StreamServer2 on my windows 10 computer, byt when i run it on my 2016 server, i get an error saying : Output file #0 does not contain any stream

  I works on my Windows 10 computer, also I have an old version of StreamServer2 from before we created the control channel ; that one is opning a RTSP stream as you normally will do, bu calling the rtsp url, and that is currently running live on an server 2008R2 environment.

  The reason that we did change the way of getting a stream is that we have a new system where the DVRs IPAddress is dynamic and unpredictable.

  So i hope that somebody can help me find out why it does not work on Windows Server 2016

  The FFMPG Report file

  ffmpeg started on 2018-06-27 at 13:06:51
  
  Report written to "ffmpeg-20180627-130651.log"
  
  Command line:
  
  "E:\\r2pPrograms\\StreamServer2\\ffmpeg.exe" -stdin -y -loglevel info -report -protocol_whitelist file,udp,rtp -i 8936021605650268160_37.sdp -f mpeg1video -g 52 -movflags frag_keyframe+empty_moov -b:v 64k -q 5 -an -
  
  ffmpeg version N-91024-g293a6e8332 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 7.3.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
  
    libavutil      56. 18.100 / 56. 18.100
  
    libavcodec     58. 19.101 / 58. 19.101
  
    libavformat    58. 13.102 / 58. 13.102
  
    libavdevice    58.  4.100 / 58.  4.100
  
    libavfilter     7. 21.100 /  7. 21.100
  
    libswscale      5.  2.100 /  5.  2.100
  
    libswresample   3.  2.100 /  3.  2.100
  
    libpostproc    55.  2.100 / 55.  2.100
  
  Splitting the commandline.
  
  Reading option '-stdin' ... matched as option 'stdin' (enable or disable interaction on standard input) with argument '1'.
  
  Reading option '-y' ... matched as option 'y' (overwrite output files) with argument '1'.
  
  Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'info'.
  
  Reading option '-report' ... matched as option 'report' (generate a report) with argument '1'.
  
  Reading option '-protocol_whitelist' ... matched as AVOption 'protocol_whitelist' with argument 'file,udp,rtp'.
  
  Reading option '-i' ... matched as input url with argument '8936021605650268160_37.sdp'.
  
  Reading option '-f' ... matched as option 'f' (force format) with argument 'mpeg1video'.
  
  Reading option '-g' ... matched as AVOption 'g' with argument '52'.
  
  Reading option '-movflags' ... matched as AVOption 'movflags' with argument 'frag_keyframe+empty_moov'.
  
  Reading option '-b:v' ... matched as option 'b' (video bitrate (please use -b:v)) with argument '64k'.
  
  Reading option '-q' ... matched as option 'q' (use fixed quality scale (VBR)) with argument '5'.
  
  Reading option '-an' ... matched as option 'an' (disable audio) with argument '1'.
  
  Reading option '-' ... matched as output url.
  
  Finished splitting the commandline.
  
  Parsing a group of options: global .
  
  Applying option stdin (enable or disable interaction on standard input) with argument 1.
  
  Applying option y (overwrite output files) with argument 1.
  
  Applying option loglevel (set logging level) with argument info.
  
  Applying option report (generate a report) with argument 1.
  
  Successfully parsed a group of options.
  
  Parsing a group of options: input url 8936021605650268160_37.sdp.
  
  Successfully parsed a group of options.
  
  Opening an input file: 8936021605650268160_37.sdp.
  
  [NULL @ 000001484256c1c0] Opening '8936021605650268160_37.sdp' for reading
  
  [sdp @ 000001484256c1c0] Format sdp probed with size=2048 and score=50
  
  [sdp @ 000001484256c1c0] video codec set to: h264
  
  [udp @ 0000014842572700] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 0000014842572700] end receive buffer size reported is 65536
  
  [udp @ 000001484258f140] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
  
  [udp @ 000001484258f140] end receive buffer size reported is 65536
  
  [sdp @ 000001484256c1c0] setting jitter buffer size to 500
  
  [sdp @ 000001484256c1c0] Before avformat_find_stream_info() pos: 152 bytes read:152 seeks:0 nb_streams:1
  
  [sdp @ 000001484256c1c0] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
  
  Consider increasing the value for the 'analyzeduration' and 'probesize' options
  
  [sdp @ 000001484256c1c0] After avformat_find_stream_info() pos: 152 bytes read:152 seeks:0 frames:0
  
  Input #0, sdp, from '8936021605650268160_37.sdp':
  
    Duration: N/A, bitrate: N/A
  
      Stream #0:0, 0, 1/90000: Video: h264, none, 90k tbr, 90k tbn, 180k tbc
  
  Successfully opened the file.
  
  Parsing a group of options: output url -.
  
  Applying option f (force format) with argument mpeg1video.
  
  Applying option b:v (video bitrate (please use -b:v)) with argument 64k.
  
  Applying option q (use fixed quality scale (VBR)) with argument 5.
  
  Applying option an (disable audio) with argument 1.
  
  Successfully parsed a group of options.
  
  Opening an output file: -.
  
  Output #0, mpeg1video, to 'pipe:':
  
  Output file #0 does not contain any stream
  
  [AVIOContext @ 0000014842574b80] Statistics: 152 bytes read, 0 seeks

• passing options in execFileSync fails for ffmpeg

  17 octobre 2018, par Amin Baig

  I am trying to write a small scripts to automate the creation of video files. I have it almost working but stuck at one part, following is my node js code :

  let str1 = "-c:v libvpx -i sourceVideos/a1.mkv -c:v libvpx -i sourceVideos/a2.mkv -c:v libvpx -i sourceVideos/a3.mkv";
  
  let str2 = "[1]setpts=PTS+5.00/TB[a2];[2]setpts=PTS+10.00/TB[a3];[0][a2]overlay[o2];[o2][a3]overlay";
  
  let outFile = 'validout.mp4';
  
  const masterStream = execFileSync('ffmpeg', [str1, '-filter_complex', str2, outFile]);
  
  
  
  console.log('All processing completed');

  The above code represents this ffmpeg command to create a video from multiple videos :

  ffmpeg -c:v libvpx -i sourceVideos/a1.mkv -c:v libvpx -i sourceVideos/a2.mkv -c:v libvpx -i sourceVideos/a3.mkv -filter_complex "[1]setpts=PTS+5.00/TB[a2];[2]setpts=PTS+10.00/TB[a3];[0][a2]overlay[o2];[o2][a3]overlay" validationout.mp4

  So I have placed the args in str2 and the options/inputs in str1. The problem is that when I pass the inputs with their options in str1 and place it in my execFileSync command it’s not parsed by the command. I have also tested for confirmation and if I pass the options in the following format it works in the node js script :

  //version 1 with separated arguments
  
  const masterStream = execFileSync('ffmpeg', ['-c:v', 'libvpx', '-i', 'sourceVideos/a1.mkv', '-c:v', 'libvpx', '-i', 'sourceVideos/a2.mkv', '-c:v', 'libvpx', '-i', 'sourceVideos/a3.mkv', '-filter_complex', str2, outFile]);

  My question is : how can I pass the options/inputs to the execFileSync in str1 so that they can be executed ?