Day to Day Code by Chathumina Vimukthi

  Prerequisites  Keycloak server should be up and running  By default Keycloak will start on http://localhost:8180 To install and configure Keycloak visit www.keycloak.org/docs/latest/getting_started/index.html. Gitlab must be installed locally By default Gitlab starts on http://localhost:3000 To install and configure Gitlab visit https://docs.gitlab.com/omnibus/manual_install.html Environment Gitlab Installed package - gitlab-ce_11.1.4-ce.0_amd64.deb (Omnibus package) Keycloak version - Version 4.2.1.Finalhttps://github.com/ChathuminaVimukthi/Gitlab-SSO-implementation-using-Keycloak SSO Configuration GitLab can be configured to act as a SAML 2.0 Service Provider (SP). This allows GitLab to consume assertions from a SAML 2.0 Identity Provider (IdP) to authenticate users. For this SSO implementation, Gitlab omnibus package is used. But the source package can be used as well. The configuration for the source packge is available on https:/...

Regardless of the  package manager  you’re using, you have two ways of installing programs on Linux. You either use a pre-built package, or compile it yourself. These days, the former usually wins out by default. There are, however, times when you should consider the alternative. What Are Binary Packages? Installing programs on Linux is usually quite different to installing on Windows. Rather than get the installers off a vendor’s website, the files are retrieved from a repository of programs, usually  tailored  for your operating system. Files for separate programs are stored in an  archive format . This bundles everything into a single file for easy access later. For example, Debian uses the DEB format to store their programs. These bundles are called  binary packages . Installing requires a special program to extract these files and put them onto your computer. That is to say, your package manager (e.g. APT, Yum, and so on). It also doe...

   Why we should use Binary Installation without using apt in U buntu? The difference is that apt installs generic binaries and manages their versions. When compiling a source package you are entirely on your own because apt cannot manage the package. However, compiling a source package and installing it yourself is useful if you need features that can be had only by compiling the package yourself. Sometimes developers will provide features that can only be used in software if a certain compiler switch is used. And sometimes specific processors can perform better if certain compile flags are used.   However, in most cases the features that can be enabled are for debugging purp oses and will never be needed even by hard core users. And the binary version that apt is configured to use is already optimized for your processor. Possible situations where you would need to compile the source yourself would be: There's a version of the software available th...

THE ALIAS COMMAND The alias command makes it possible to launch any command or group of commands (inclusive of any options, arguments and redirection) by entering a pre-set string (i.e., sequence of characters). CREATING ALIASES The general syntax for the alias command varies somewhat according to the shell. In the case of the bash shell it is alias [-p] [name="value"] Aliases can be created in the .bashrc file in Ubuntu home directory. But without manipulating the .bashrc , it is the best practice to create a new file . bash _aliases in the home directory. The .bashrc is a hidden file and if you don't see a file like this in home directory , press ctrl+h to unhide all the hidden files and folders. These are hidden because they are not to be edited . But in our case we need to edit these a little bit but carefully. After creating the .bash_aliases open the .bashrc file in the home directory and check if the bellow code snippet is in t...