Thanks Chathuri, Looks like this config is using OAuth vs the basic authentication mode. If I use this then it does a nice job of logging me into the dev server, however, if I change the callback URI to point back to my local development instance then it complains that the callback URI is not registered. I don’t imagine you want to register development instance callback URIs so is there any chance you can send me a working example using the basic authentication approach?
S. > On Sep 28, 2015, at 1:46 PM, Chathuri Wimalasena <[email protected]> wrote: > > One correction that I saw is 'airavata-port' should be 8930 instead of 9930. > Also I see tokens are different too.. I'm attaching the pga_config.file of > the dev server for your reference. You can use the same config file. > > Thanks.. > Chathuri > > On Mon, Sep 28, 2015 at 3:39 PM, Simon Twigger <[email protected] > <mailto:[email protected]>> wrote: > The pga_config.php is the same as the one in github > (https://github.com/apache/airavata-php-gateway/blob/master/app/config/pga_config.php.template > > <https://github.com/apache/airavata-php-gateway/blob/master/app/config/pga_config.php.template>) > which looks like it should use the master PGA and the gw56 xsede airavata > instance. > > I tried [email protected] <mailto:[email protected]>/master and it > comes back with invalid username/password. > > S. > > > >> On Sep 28, 2015, at 12:35 PM, Chathuri Wimalasena <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Simon, >> >> I'm assuming you are using master PGA which points to gw56.iu.xsede.org >> <http://gw56.iu.xsede.org/> airavata instance and identity server >> https://idp.scigap.org:7443/ <https://idp.scigap.org:7443/>. If so, you >> should be able to login as admin using following username and password. >> >> 'admin-username' => '[email protected] <mailto:[email protected]>' >> 'admin-password' => 'master' >> >> Please let us know if you face any issues. If possible, share pga_config.php >> with us so we can assist you more. >> >> Thanks.. >> Chathuri >> >> >> >> On Mon, Sep 28, 2015 at 1:56 PM, Simon Twigger <[email protected] >> <mailto:[email protected]>> wrote: >> Hi Eroma, >> >> Thanks for the reply. >> >> The ‘user-role-name’ is currently set to 'airavata-user’ in the >> pga_config.php. How do I log in as the admin user to check this on the admin >> interface? The pga_config.php has 'tenant admin' username and password >> settings but these do not seem to work to log in so should I be looking >> somewhere else for the appropriate username/password? >> >> Cheers, >> >> Simon. >> >> >> >>> On Sep 28, 2015, at 11:44 AM, Eroma Abeysinghe <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi Simon, >>> >>> I am not sure wether pga theming has anything to do with the user not been >>> able to view the menus. >>> >>> Could you please try below and see wether it helps? >>> In latest PGA when a user is newly created the user is assigned the role of >>> Internal/Everyone. For this user there are no menus available. >>> Could you please check the role of your new user by login to gateway as the >>> admin? (Once login please navigate to PGA --> Admin Dashboard-->Users) >>> If its Internal/Everyone then please change it to airavata-user; this role >>> can view the menus and do operations in the gateway. >>> >>> Hope this helps till Nipurn replies. >>> >>> Thanks, >>> Eroma >>> >>> On Mon, Sep 28, 2015 at 1:09 PM, Simon Twigger <[email protected] >>> <mailto:[email protected]>> wrote: >>> Hi Nipun, >>> >>> Thanks for the update on the theming - I’ve been giving this a try using >>> the latest master branch, its generally being working pretty well but I >>> have had a few issues: >>> >>> To make things easier, I’m passing in the theme name via a PGA_THEME >>> environment variable that is referred to in BaseController.php so its >>> easier or me to change the theme being used. >>> >>> The header and footer and template.blade.php partials seem to work fine, I >>> can see these as expected. >>> >>> I copied the pga_config.php.template over to pga_config.php to use the >>> provided defaults, I can create a new user but when I log in I don’t see >>> any of the Project, Experiment or Help menus that I would normally see. >>> Looking at CommonUtilities.php this may be because some Session variables >>> are not being set correctly e.g. ‘authorized_user’ doesn’t seem to be set. >>> >>> Might this have something to do with the theme or the pga_config settings >>> or something else? >>> >>> Is there any documentation on the pga_config.php settings and what they >>> mean? >>> >>> Any thoughts on this would be most appreciated! >>> >>> Cheers, >>> >>> Simon. >>> >>> >>> >>> Other things I’ve come across: >>> >>> >>> I had to edit views/layout/basic_blade.php which was giving some javascript >>> errors when setting these two var's because the original code had a mixture >>> of syntaxes >>> >>> <!-- Getting user info --> >>> @if(Session::has("user-profile")) >>> <script> >>> var email = '{{ Session::get("user-profile")["email"] }}' >>> var fullName = '{{ Session::get("user-profile")["firstname"] . " " . >>> Session::get("user-profile")["lastname"] }}' >>> </script> >>> @endif >>> >>> -- >>> Simon Twigger, Ph.D. >>> Senior Scientific Consultant >>> BioTeam - Enabling Science, http://bioteam.net <http://bioteam.net/> >>> >>> Email: [email protected] <mailto:[email protected]> >>> Tel: 1-303-991-0459 <tel:1-303-991-0459> >>> Toll Free: 1-877-246-2992 Ext. 111 <tel:1-877-246-2992%20Ext.%20111> >>> >>> >>> >>>> On Sep 18, 2015, at 9:43 AM, Nipurn Doshi <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi Simon, >>>> >>>> I have been working on creating Theming feature possible for PGA >>>> interfaces. This would help all portals that are trying to use PGA to >>>> apply their global theme options on top of PGA. >>>> >>>> I have committed first iteration of code to master. To get the most out of >>>> theming options I would like to explain how it works - >>>> >>>> A "themes" folder has been added to the root. This will contain all themes >>>> that users want to use. At the moment, it contains a "base" theme that >>>> forms the default/sample theme applied on PGA. Following are the steps for >>>> creating your own theme - >>>> After updating the code, you will have to run "composer update" in the >>>> root for the new theming package to set in. >>>> Copy paste the "base" folder in the same "themes" directory and rename it >>>> to the what you want your theme name to be. >>>> Open app/controllers/BaseController.php and change the theme name from >>>> "base" to what your theme name is, on lines 13 and 14. >>>> Open themes/<theme-name>/partials/header.blade.php. Here, you can add >>>> global header and style settings in the form of css for your portal that >>>> you want to have all across the web application. >>>> Open themes/<theme-name>/partials/header.blade.php. Here, you can add >>>> global footer and script settings in the form of js for your portal that >>>> you want to have all across the web application. >>>> Open themes/<theme-name>/partials/template.blade.php. Here, you can add >>>> the Landing page template that you would like your users would want to see >>>> on the website before logging in to PGA. >>>> You can also put your css and js files in themes/<theme-name>/assets and >>>> call them relatively into header/footer/template. >>>> >>>> Please let me know if you run into any issues. I'll be happy to help. >>> >>> >>> >>> >>> -- >>> Thank You, >>> Best Regards, >>> Eroma >> >> > > > <pga_config.php>
